From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-linus][PATCH 0/2] tracefs: Fixes for 7.1
Date: Mon, 20 Apr 2026 14:11:51 -0400 [thread overview]
Message-ID: <20260420181151.771404678@kernel.org> (raw)
tracefs fixes for v7.1:
- Use list_add_tail_rcu() for walking eventfs children
The children link list is protected by SRCU and list walkers can walk the
list without the lock and only using SRCU. Using just list_add_tail() on
weakly ordered architectures can cause issues. Instead use
list_add_tail_rcu().
- Hold eventfs_mutex and SRCU for remount walk events
The trace_apply_options() walks the tracefs_inodes where some are eventfs
inodes and eventfs_remount() is called which in turn calls
eventfs_set_attr(). This walk only holds normal RCU read locks, but the
eventfs_mutex and SRCU should be held. Add a eventfs_remount_(un)lock()
helpers to take the necessary locks before iterating the list.
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
tracefs/fixes
Head SHA1: 07004a8c4b572171934390148ee48c4175c77eed
David Carlier (2):
eventfs: Use list_add_tail_rcu() for SRCU-protected children list
eventfs: Hold eventfs_mutex and SRCU when remount walks events
----
fs/tracefs/event_inode.c | 16 +++++++++++++++-
fs/tracefs/inode.c | 5 ++++-
fs/tracefs/internal.h | 3 +++
3 files changed, 22 insertions(+), 2 deletions(-)
next reply other threads:[~2026-04-20 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 18:11 Steven Rostedt [this message]
2026-04-20 18:11 ` [for-linus][PATCH 1/2] eventfs: Use list_add_tail_rcu() for SRCU-protected children list Steven Rostedt
2026-04-20 18:11 ` [for-linus][PATCH 2/2] eventfs: Hold eventfs_mutex and SRCU when remount walks events Steven Rostedt
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=20260420181151.771404678@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
/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