From: Petr Pavlu <petr.pavlu@suse.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tom Zanussi <zanussi@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Petr Pavlu <petr.pavlu@suse.com>
Subject: [PATCH v2 0/4] Clean up access to trace_event_file from a file struct
Date: Mon, 16 Feb 2026 14:41:56 +0100 [thread overview]
Message-ID: <20260216134247.1311631-1-petr.pavlu@suse.com> (raw)
This series includes several patches related to accessing
trace_event_file from a file struct. The first patch is a fix for an
edge case, the remaining patches are minor cleanups.
Changes since v1 [1]:
* Fix a compilation error when CONFIG_HIST_TRIGGERS is not set.
* Drop a patch that references the trace_event_file data in
event_file_data() and keep the simpler implementation of storing the
id in i_private.
* Inline event_file_data() into event_id_read() to enable adding
additional checks to the former.
Petr Pavlu (4):
tracing: Fix checking of freed trace_event_file for hist files
tracing: Remove unnecessary check for EVENT_FILE_FL_FREED
tracing: Clean up access to trace_event_file from a file pointer
tracing: Free up file->private_data for use by individual events
include/linux/trace_events.h | 5 +++++
kernel/trace/trace.c | 2 --
kernel/trace/trace.h | 17 +++++++++++------
kernel/trace/trace_events.c | 17 ++++++++---------
kernel/trace/trace_events_hist.c | 8 ++------
5 files changed, 26 insertions(+), 23 deletions(-)
base-commit: cee73b1e840c154f64ace682cb477c1ae2e29cc4
--
2.52.0
next reply other threads:[~2026-02-16 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 13:41 Petr Pavlu [this message]
2026-02-16 13:41 ` [PATCH v2 1/4] tracing: Fix checking of freed trace_event_file for hist files Petr Pavlu
2026-02-17 15:29 ` Steven Rostedt
2026-02-19 0:01 ` Steven Rostedt
2026-02-16 13:41 ` [PATCH v2 2/4] tracing: Remove unnecessary check for EVENT_FILE_FL_FREED Petr Pavlu
2026-02-16 13:41 ` [PATCH v2 3/4] tracing: Clean up access to trace_event_file from a file pointer Petr Pavlu
2026-02-16 13:42 ` [PATCH v2 4/4] tracing: Free up file->private_data for use by individual events Petr Pavlu
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=20260216134247.1311631-1-petr.pavlu@suse.com \
--to=petr.pavlu@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=zanussi@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