From: Zqiang <qiang.zhang@linux.dev>
To: aahringo@redhat.com, teigland@redhat.com
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
qiang.zhang@linux.dev
Subject: [PATCH] dlm: wait for outstanding SRCU callbacks to complete in exit paths
Date: Tue, 1 Sep 2026 17:18:36 +0800 [thread overview]
Message-ID: <20260901091836.16906-1-qiang.zhang@linux.dev> (raw)
The dlm_lowcomms_exit() and dlm_midcomms_exit() iterate over the
srcu protected connection and node hash tables and hand each
element to call_srcu() for deferred freeing (connection_release()
and midcomms_node_release()). call_srcu() is asynchronous: the
callbacks are invoked only after an SRCU grace period, which may
happen after the exit function has already returned.
These exit functions are reached from exit_dlm() on module unload.
Once they return, module teardown continues and the module text
may be unloaded while call_srcu() callbacks are still pending. When
such a callback finally runs, it executes freed module code and
touches the static SRCU domains that are being torn down, resulting
in a use-after-free.
Add an srcu_barrier() after the call_srcu() loop in each exit function
to wait for all outstanding callbacks of the respective SRCU domain to
complete before returning. In dlm_midcomms_exit() the barrier is issued
before dlm_lowcomms_exit() so that node callbacks are drained prior to
tearing down the lower layer.
Signed-off-by: Zqiang <qiang.zhang@linux.dev>
---
fs/dlm/lowcomms.c | 1 +
fs/dlm/midcomms.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 2aff1c7c17de..ea8353c4638d 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -1984,4 +1984,5 @@ void dlm_lowcomms_exit(void)
}
}
srcu_read_unlock(&connections_srcu, idx);
+ srcu_barrier(&connections_srcu);
}
diff --git a/fs/dlm/midcomms.c b/fs/dlm/midcomms.c
index 8964164600d2..045431524494 100644
--- a/fs/dlm/midcomms.c
+++ b/fs/dlm/midcomms.c
@@ -1178,6 +1178,7 @@ void dlm_midcomms_exit(void)
}
}
srcu_read_unlock(&nodes_srcu, idx);
+ srcu_barrier(&nodes_srcu);
dlm_lowcomms_exit();
}
--
2.17.1
next reply other threads:[~2026-09-01 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:18 Zqiang [this message]
2026-09-01 17:12 ` [PATCH] dlm: wait for outstanding SRCU callbacks to complete in exit paths Alexander Aring
2026-09-02 13:21 ` Alexander Aring
2026-09-02 14:15 ` Zqiang
2026-09-02 14:29 ` Zqiang
2026-09-02 14:36 ` Alexander Aring
2026-09-02 14:49 ` Zqiang
2026-09-02 15:02 ` Alexander Aring
2026-09-02 14:30 ` Alexander Aring
2026-09-02 14:48 ` Alexander Aring
2026-09-02 16:44 ` Paul E. McKenney
2026-09-02 17:13 ` Alexander Aring
2026-09-02 20:05 ` Paul E. McKenney
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=20260901091836.16906-1-qiang.zhang@linux.dev \
--to=qiang.zhang@linux.dev \
--cc=aahringo@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.