linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Thomas Falcon <thomas.falcon@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: write bpf_prog (infos|btfs)_cnt to data file
Date: Thu, 13 Nov 2025 23:21:48 -0800	[thread overview]
Message-ID: <aRbYjFLCpLAFrMWD@google.com> (raw)
In-Reply-To: <aRXUmEfApr9UTfsY@x1>

On Thu, Nov 13, 2025 at 09:52:40AM -0300, Arnaldo Carvalho de Melo wrote:
> On Tue, Nov 11, 2025 at 02:38:07PM -0800, Namhyung Kim wrote:
> > On Fri, Nov 07, 2025 at 11:31:50AM -0600, Thomas Falcon wrote:
> > > With commit f0d0f978f3f58 ("perf header: Don't write empty BPF/BTF
> > > info"), the write_bpf_( prog_info() | btf() ) functions exit
> > > without writing anything if env->bpf_prog.(infos| btfs)_cnt is zero.
> > > 
> > > process_bpf_( prog_info() | btf() ), however, still expect a "count"
> > > value to exist in the data file. If btf information is empty, for
> > > example, process_bpf_btf will read garbage or some other data as the
> > > number of btf nodes in the data file. As a result, the data file will
> > > not be processed correctly.
> > > 
> > > Instead, write the count to the data file and exit if it is zero.
> > 
> > Oh, I'm afraid it'd create a compatibility problem.  But I think this is
> > a right behavior and it's should be fine if it goes to the stable soon.
> > 
> > Arnaldo, can you please take this into perf-tools tree for v6.18?
> 
> Ok, agreed, I'm taking your request as an Acked-by, ok?

Sure, thanks!
Namhyung

> > 
> > > 
> > > Fixes: f0d0f978f3f58 ("perf header: Don't write empty BPF/BTF info")
> > > Signed-off-by: Thomas Falcon <thomas.falcon@intel.com>
> > > ---
> > >  tools/perf/util/header.c | 10 ++--------
> > >  1 file changed, 2 insertions(+), 8 deletions(-)
> > > 
> > > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> > > index db2ad19fa50d..54968881481c 100644
> > > --- a/tools/perf/util/header.c
> > > +++ b/tools/perf/util/header.c
> > > @@ -1022,12 +1022,9 @@ static int write_bpf_prog_info(struct feat_fd *ff,
> > >  
> > >  	down_read(&env->bpf_progs.lock);
> > >  
> > > -	if (env->bpf_progs.infos_cnt == 0)
> > > -		goto out;
> > > -
> > >  	ret = do_write(ff, &env->bpf_progs.infos_cnt,
> > >  		       sizeof(env->bpf_progs.infos_cnt));
> > > -	if (ret < 0)
> > > +	if (ret < 0 || env->bpf_progs.infos_cnt == 0)
> > >  		goto out;
> > >  
> > >  	root = &env->bpf_progs.infos;
> > > @@ -1067,13 +1064,10 @@ static int write_bpf_btf(struct feat_fd *ff,
> > >  
> > >  	down_read(&env->bpf_progs.lock);
> > >  
> > > -	if (env->bpf_progs.btfs_cnt == 0)
> > > -		goto out;
> > > -
> > >  	ret = do_write(ff, &env->bpf_progs.btfs_cnt,
> > >  		       sizeof(env->bpf_progs.btfs_cnt));
> > >  
> > > -	if (ret < 0)
> > > +	if (ret < 0 || env->bpf_progs.btfs_cnt == 0)
> > >  		goto out;
> > >  
> > >  	root = &env->bpf_progs.btfs;
> > > -- 
> > > 2.47.3
> > > 

      reply	other threads:[~2025-11-14  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 17:31 [PATCH] perf: write bpf_prog (infos|btfs)_cnt to data file Thomas Falcon
2025-11-11 22:07 ` Ian Rogers
2025-11-11 22:38 ` Namhyung Kim
2025-11-13 12:52   ` Arnaldo Carvalho de Melo
2025-11-14  7:21     ` Namhyung Kim [this message]

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=aRbYjFLCpLAFrMWD@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=thomas.falcon@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;
as well as URLs for NNTP newsgroup(s).