From: Alexander Aring <aahringo@redhat.com>
To: teigland@redhat.com
Cc: cluster-devel@redhat.com
Subject: [Cluster-devel] [PATCHv2 dlm-next 04/13] fs: dlm: check on plock ops when exit dlm
Date: Tue, 1 Aug 2023 14:09:41 -0400 [thread overview]
Message-ID: <20230801180950.3693180-5-aahringo@redhat.com> (raw)
In-Reply-To: <20230801180950.3693180-1-aahringo@redhat.com>
To be sure we don't have any issues that there are leftover plock ops in
either send_list or recv_list we simple check if either one of the list
are empty when we exit the dlm subsystem.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
---
fs/dlm/plock.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/dlm/plock.c b/fs/dlm/plock.c
index 44b3aab5b709..5c2cc8d940ef 100644
--- a/fs/dlm/plock.c
+++ b/fs/dlm/plock.c
@@ -628,5 +628,7 @@ int dlm_plock_init(void)
void dlm_plock_exit(void)
{
misc_deregister(&plock_dev_misc);
+ WARN_ON(!list_empty(&send_list));
+ WARN_ON(!list_empty(&recv_list));
}
--
2.31.1
next prev parent reply other threads:[~2023-08-01 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 18:09 [Cluster-devel] [PATCHv2 dlm-next 00/13] fs: dlm: miscs and msgs processing changes Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 01/13] fs: dlm: add missing spin_unlock Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 02/13] fs: dlm: remove unused processed_nodes Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 03/13] fs: dlm: debugfs for queued callbacks Alexander Aring
2023-08-01 18:09 ` Alexander Aring [this message]
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 05/13] fs: dlm: add plock dev tracepoints Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 06/13] fs: dlm: remove clear_members_cb Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 07/13] fs: dlm: cleanup lock order Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 08/13] fs: dlm: get recovery sequence number as parameter Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 09/13] fs: dlm: drop rxbuf manipulation in dlm_copy_master_names Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 10/13] fs: dlm: drop rxbuf manipulation in dlm_recover_master_copy Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 11/13] fs: dlm: constify receive buffer Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 12/13] fs: dlm: create midcomms nodes when configure Alexander Aring
2023-08-01 18:09 ` [Cluster-devel] [PATCHv2 dlm-next 13/13] fs: dlm: don't use RCOM_NAMES for version detection Alexander Aring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230801180950.3693180-5-aahringo@redhat.com \
--to=aahringo@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=teigland@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).