From: Ye Liu <ye.liu@linux.dev>
To: "Mickaël Salaün" <mic@digikod.net>,
"Paul Moore" <paul@paul-moore.com>,
"James Morris" <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>
Cc: "Ye Liu" <liuye@kylinos.cn>, "Günther Noack" <gnoack@google.com>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 8/8] security/landlock: convert thread iterator to for_each_thread_rcu
Date: Fri, 4 Sep 2026 16:30:00 +0800 [thread overview]
Message-ID: <20260904083001.553587-9-ye.liu@linux.dev> (raw)
In-Reply-To: <20260904083001.553587-1-ye.liu@linux.dev>
From: Ye Liu <liuye@kylinos.cn>
Replace guard(rcu)() + for_each_thread() with for_each_thread_rcu(),
so that the RCU read-side critical section is scoped to the loop body.
No functional change.
Signed-off-by: Ye Liu <liuye@kylinos.cn>
---
security/landlock/tsync.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/security/landlock/tsync.c b/security/landlock/tsync.c
index 0b71e158c3f5..f1c08aae179b 100644
--- a/security/landlock/tsync.c
+++ b/security/landlock/tsync.c
@@ -335,9 +335,7 @@ static size_t count_additional_threads(const struct tsync_works *works)
caller = current;
- guard(rcu)();
-
- for_each_thread(caller, thread) {
+ for_each_thread_rcu(caller, thread) {
/* Skip current, since it is initiating the sync. */
if (thread == caller)
continue;
@@ -376,9 +374,7 @@ static bool schedule_task_work(struct tsync_works *works,
caller = current;
- guard(rcu)();
-
- for_each_thread(caller, thread) {
+ for_each_thread_rcu(caller, thread) {
/* Skip current, since it is initiating the sync. */
if (thread == caller)
continue;
--
2.25.1
next prev parent reply other threads:[~2026-09-04 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 8:29 [PATCH 0/8] mm: introduce for_each_process_rcu and for_each_thread_rcu Ye Liu
2026-09-04 8:30 ` Ye Liu [this message]
2026-09-04 12:21 ` [PATCH 8/8] security/landlock: convert thread iterator to for_each_thread_rcu Justin Suess
2026-09-04 14:17 ` Günther Noack
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=20260904083001.553587-9-ye.liu@linux.dev \
--to=ye.liu@linux.dev \
--cc=gnoack@google.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=liuye@kylinos.cn \
--cc=mic@digikod.net \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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