From: Steven Rostedt <rostedt@goodmis.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/3] tracing: More fixes for v6.7-rc6
Date: Thu, 21 Dec 2023 10:09:22 -0500 [thread overview]
Message-ID: <20231221150922.017965539@goodmis.org> (raw)
Tracing fixes for 6.7:
- Fix another kerneldoc warning
- Fix eventfs files to inherit the ownership of its parent directory.
The dynamic creating of dentries in eventfs did not take into
account if the tracefs file system was mounted with a gid/uid,
and would still default to the gid/uid of root. This is a regression.
- Fix warning when synthetic event testing is enabled along with
startup event tracing testing is enabled
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/urgent
Head SHA1: 88b30c7f5d27e1594d70dc2bd7199b18f2b57fa9
Randy Dunlap (1):
tracing/synthetic: fix kernel-doc warnings
Steven Rostedt (Google) (2):
eventfs: Have event files and directories default to parent uid and gid
tracing / synthetic: Disable events after testing in synth_event_gen_test_init()
----
fs/tracefs/event_inode.c | 12 +++++++++---
kernel/trace/synth_event_gen_test.c | 11 +++++++++++
kernel/trace/trace_events_synth.c | 4 ++--
3 files changed, 22 insertions(+), 5 deletions(-)
next reply other threads:[~2023-12-21 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:09 Steven Rostedt [this message]
2023-12-21 15:09 ` [for-linus][PATCH 1/3] tracing/synthetic: fix kernel-doc warnings Steven Rostedt
2023-12-21 15:09 ` [for-linus][PATCH 2/3] eventfs: Have event files and directories default to parent uid and gid Steven Rostedt
2023-12-21 15:09 ` [for-linus][PATCH 3/3] tracing / synthetic: Disable events after testing in synth_event_gen_test_init() 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=20231221150922.017965539@goodmis.org \
--to=rostedt@goodmis.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