From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ajay Kaher <akaher@vmware.com>,
kernel test robot <oliver.sang@intel.com>,
Ching-lin Yu <chinglinyu@google.com>
Subject: [PATCH 0/2] tracing: Add missing LOCKDOWN_TRACEFS checking
Date: Tue, 05 Sep 2023 14:26:07 -0400 [thread overview]
Message-ID: <20230905182607.505212458@goodmis.org> (raw)
When LOCKDOWN_TRACEFS is activated, some of the tracefs functions can
still return success leaving tracefs in an undefined state.
I broke this up into two patches. One that fixes just tracefs that
existed before this merge window and needs to be backported to stable.
The other fixes changes added to this merge window.
This should fix the issue reported by kernel test robot:
https://lore.kernel.org/all/202309050916.58201dc6-oliver.sang@intel.com/
Steven Rostedt (Google) (2):
tracefs: Add missing lockdown check to tracefs_create_dir()
tracefs/eventfs: Add missing lockdown checks
----
fs/tracefs/event_inode.c | 15 +++++++++++++++
fs/tracefs/inode.c | 3 +++
2 files changed, 18 insertions(+)
next reply other threads:[~2023-09-05 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 18:26 Steven Rostedt [this message]
2023-09-05 18:26 ` [PATCH 1/2] tracefs: Add missing lockdown check to tracefs_create_dir() Steven Rostedt
2023-09-05 18:26 ` [PATCH 2/2] tracefs/eventfs: Add missing lockdown checks 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=20230905182607.505212458@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akaher@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=chinglinyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=oliver.sang@intel.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