Linux Trace Development
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Li Pengfei <ljdlns1987@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtracefs: Pass the pipe size by value to F_SETPIPE_SZ
Date: Sat, 7 Nov 2026 17:40:11 -0500	[thread overview]
Message-ID: <20261107174011.7d86b1de@fedora> (raw)
In-Reply-To: <20261107140755.2983258-1-lipengfei28@xiaomi.com>

On Sat,  7 Nov 2026 22:07:55 +0800
Li Pengfei <ljdlns1987@gmail.com> wrote:

> F_SETPIPE_SZ takes the new size as the argument itself, but init_splice()
> passes a pointer to it.  The kernel takes that argument as an unsigned int,
> so the pointer is truncated to its low 32 bits and used as the size.  That
> usually fails, leaving the pipe at the default 64K, so a sub buffer larger
> than that no longer fits in one splice() and the recorders lose data.  It
> can also succeed at an unrelated size with no error to notice.
> 
> Failing here stays non fatal, as an unprivileged caller cannot raise a pipe
> above /proc/sys/fs/pipe-max-size and the default size still records.

Good catch!

> 
> While here, drop the third argument from the F_GETPIPE_SZ call next to it.
> That command takes no argument and returns the size, so the pointer was
> never read and the return value was already being used.  The branch it fed
> was unreachable: F_GETPIPE_SZ never returns zero on success.
> 
> Signed-off-by: Li Pengfei <lipengfei28@xiaomi.com>
> ---
>  src/tracefs-record.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/src/tracefs-record.c b/src/tracefs-record.c
> index 21a2f6b..9ef13e0 100644
> --- a/src/tracefs-record.c
> +++ b/src/tracefs-record.c
> @@ -554,20 +554,22 @@ static int init_splice(struct tracefs_cpu *tcpu)
>  
>  	if (tfs_str_read_file("/proc/sys/fs/pipe-max-size", &buf, false) > 0) {
>  		int size = atoi(buf);
> -		fcntl(tcpu->splice_pipe[0], F_SETPIPE_SZ, &size);
> +
> +		/* F_SETPIPE_SZ takes the size itself, not a pointer to it */

Nit. You don't need to add comments to bug fixes. That is, the above
comment is useless.

Thanks,

-- Steve



> +		fcntl(tcpu->splice_pipe[0], F_SETPIPE_SZ, size);
>  		free(buf);
>  	}
>  
> -	ret = fcntl(tcpu->splice_pipe[0], F_GETPIPE_SZ, &tcpu->pipe_size);
> +	/* F_GETPIPE_SZ returns the size, it takes no third argument */
> +	ret = fcntl(tcpu->splice_pipe[0], F_GETPIPE_SZ);
>  	/*
>  	 * F_GETPIPE_SZ was introduced in 2.6.35, ftrace was introduced
>  	 * in 2.6.31. If we are running on an older kernel, just fall
> -	 * back to using subbuf_size for splice(). It could also return
> -	 * the size of the pipe and not set pipe_size.
> +	 * back to using subbuf_size for splice().
>  	 */
> -	if (ret > 0 && !tcpu->pipe_size)
> +	if (ret > 0)
>  		tcpu->pipe_size = ret;
> -	else if (ret < 0)
> +	else
>  		tcpu->pipe_size = tcpu->subbuf_size;
>  
>  	tcpu->splice_read_flags = SPLICE_F_MOVE;


  reply	other threads:[~2026-11-07 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 14:07 [PATCH] libtracefs: Pass the pipe size by value to F_SETPIPE_SZ Li Pengfei
2026-11-07 22:40 ` Steven Rostedt [this message]
2026-11-07 22:42   ` Steven Rostedt
2026-11-08  5:44     ` [PATCH v2] " Li Pengfei

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=20261107174011.7d86b1de@fedora \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=ljdlns1987@gmail.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