[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQJ0ur6Pox9aTjoSkXs43strqN__e1h4JWya46WOER9V4w@mail.gmail.com>
Date: Tue, 18 Oct 2022 21:57:18 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Peter Zijlstra <peterz@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Jiri Olsa <olsajiri@...il.com>,
Sumanth Korikkar <sumanthk@...ux.ibm.com>,
bpf <bpf@...r.kernel.org>, Vasily Gorbik <gor@...ux.ibm.com>,
Heiko Carstens <hca@...ux.ibm.com>,
Ilya Leoshkevich <iii@...ux.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Namhyung Kim <namhyung@...nel.org>,
Sven Schnelle <svens@...ux.ibm.com>,
Thomas Richter <tmricht@...ux.ibm.com>,
X86 ML <x86@...nel.org>, Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH] bpf: fix sample_flags for bpf_perf_event_output
On Fri, Oct 7, 2022 at 8:31 AM Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Fri, Oct 07, 2022 at 11:45:36AM +0200, Jiri Olsa wrote:
> > On Fri, Oct 07, 2022 at 10:13:27AM +0200, Sumanth Korikkar wrote:
> > > * Raw data is also filled by bpf_perf_event_output.
> > > * Add sample_flags to indicate raw data.
> > > * This eliminates the segfaults as shown below:
> > > Run ./samples/bpf/trace_output
> > > BUG pid 9 cookie 1001000000004 sized 4
> > > BUG pid 9 cookie 1001000000004 sized 4
> > > BUG pid 9 cookie 1001000000004 sized 4
> > > Segmentation fault (core dumped)
> > >
> > > Fixes: 838d9bb62d13 ("perf: Use sample_flags for raw_data")
> > > Acked-by: Namhyung Kim <namhyung@...nel.org>
> > > Signed-off-by: Sumanth Korikkar <sumanthk@...ux.ibm.com>
> >
> > Acked-by: Jiri Olsa <jolsa@...nel.org>
> >
> > Peter,
> > I think this should go through your tree again?
> > bpf-next/master does not have sample_flags merged yet
>
> Yep can do. I'll line it up in perf/urgent (Ingo just send out
> perf/core).
Peter,
Could you please hurry up. 11 days have passed.
This issue affects everyone the hard way now after merging
all the trees: tip -> linus -> net-next -> bpf-next.
The BPF CI is red right now with 5 tests failing because
this fix is still missing.
It's causing a headache to maintainers and developers.
Powered by blists - more mailing lists