From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Gabriele Paoloni <gpaoloni@redhat.com>
Cc: rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
acarmina@redhat.com, chuck.wolber@boeing.com
Subject: Re: [RFC PATCH 1/2] tracing: fixes of ftrace_enable_fops
Date: Fri, 13 Jun 2025 11:45:27 +0900 [thread overview]
Message-ID: <20250613114527.7e27a9a0ecc2b59d98677b0c@kernel.org> (raw)
In-Reply-To: <20250612104349.5047-2-gpaoloni@redhat.com>
On Thu, 12 Jun 2025 12:43:48 +0200
Gabriele Paoloni <gpaoloni@redhat.com> wrote:
> Currently there are different issues associated with ftrace_enable_fops
> - event_enable_write: *ppos is increased while not used at all in the
> write operation itself (following a write, this could lead a read to
> fail or report a corrupted event status);
Here, we expected the "enable" file is a pseudo text file. So if
there is a write, the ppos should be incremented.
> - event_enable_read: cnt < strlen(buf) is allowed and this can lead to
> reading an incomplete event status (i.e. not all status characters
> are retrieved) and/or reading the status in a non-atomic way (i.e.
> the status could change between two consecutive reads);
As I said, the "enable" file is a kind of text file. So reader must read
it until EOF. If you need to get the consistent result, user should
use the enough size of buffer.
> - .llseek is set to default_llseek: this is wrong since for this
> type of files it does not make sense to reposition the ppos offset.
> Hence this should be set instead to noop_llseek.
As I said, it is a kind of text file, default_llseek is better.
But, if we change (re-design) what is this "enable" file is,
we can accept these changes. So this is not a "Fix" but re-design
of the "enable" file as an interface (as a char device), not a text
file (or a block device).
I want to keep this as is, same as other tracefs files.
Thank you,
>
> This patch fixes all the issues listed above.
>
> Signed-off-by: Gabriele Paoloni <gpaoloni@redhat.com>
> Tested-by: Alessandro Carminati <acarmina@redhat.com>
> ---
> kernel/trace/trace_events.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 120531268abf..5e84ef01d0c8 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -1798,6 +1798,13 @@ event_enable_read(struct file *filp, char __user *ubuf, size_t cnt,
>
> strcat(buf, "\n");
>
> + /*
> + * A requested cnt less than strlen(buf) could lead to a wrong
> + * event status being reported.
> + */
> + if (cnt < strlen(buf))
> + return -EINVAL;
> +
> return simple_read_from_buffer(ubuf, cnt, ppos, buf, strlen(buf));
> }
>
> @@ -1833,8 +1840,6 @@ event_enable_write(struct file *filp, const char __user *ubuf, size_t cnt,
> return -EINVAL;
> }
>
> - *ppos += cnt;
> -
> return cnt;
> }
>
> @@ -2557,7 +2562,7 @@ static const struct file_operations ftrace_enable_fops = {
> .read = event_enable_read,
> .write = event_enable_write,
> .release = tracing_release_file_tr,
> - .llseek = default_llseek,
> + .llseek = noop_llseek,
> };
>
> static const struct file_operations ftrace_event_format_fops = {
> --
> 2.48.1
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2025-06-13 2:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 10:43 [RFC PATCH 0/2] tracing: ftrace_enable_fops fixes Gabriele Paoloni
2025-06-12 10:43 ` [RFC PATCH 1/2] tracing: fixes of ftrace_enable_fops Gabriele Paoloni
2025-06-13 2:45 ` Masami Hiramatsu [this message]
2025-06-19 17:07 ` Gabriele Paoloni
2025-06-20 9:35 ` Masami Hiramatsu
2025-06-20 13:26 ` Gabriele Paoloni
2025-07-01 21:58 ` Steven Rostedt
2025-07-02 14:16 ` Gabriele Paoloni
2025-06-12 10:43 ` [RFC PATCH 2/2] tracing: add testable specifications for event_enable_write/read Gabriele Paoloni
2025-07-01 22:11 ` Steven Rostedt
2025-07-02 14:59 ` Gabriele Paoloni
2025-07-02 15:12 ` Steven Rostedt
2025-07-02 16:12 ` Gabriele Paoloni
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=20250613114527.7e27a9a0ecc2b59d98677b0c@kernel.org \
--to=mhiramat@kernel.org \
--cc=acarmina@redhat.com \
--cc=chuck.wolber@boeing.com \
--cc=gpaoloni@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).