[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y6Fw1ymTcFrMR3Hl@hirez.programming.kicks-ass.net>
Date: Tue, 20 Dec 2022 09:22:47 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: sdf@...gle.com
Cc: syzbot <syzbot+b8e8c01c8ade4fe6e48f@...kaller.appspotmail.com>,
acme@...nel.org, alexander.shishkin@...ux.intel.com,
bpf@...r.kernel.org, jolsa@...nel.org,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
mark.rutland@....com, mingo@...hat.com, namhyung@...nel.org,
netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in put_pmu_ctx
On Mon, Dec 19, 2022 at 11:33:29AM -0800, sdf@...gle.com wrote:
> On 12/19, Peter Zijlstra wrote:
> > On Mon, Dec 19, 2022 at 12:04:43AM -0800, syzbot wrote:
> > > HEAD commit: 13e3c7793e2f Merge tag 'for-netdev' of
> > https://git.kernel...
> > > git tree: bpf
> > > console+strace: https://syzkaller.appspot.com/x/log.txt?x=177df7e0480000
> > > kernel config:
> > https://syzkaller.appspot.com/x/.config?x=b0e91ad4b5f69c47
> > > dashboard link:
> > https://syzkaller.appspot.com/bug?extid=b8e8c01c8ade4fe6e48f
^ so syzbot knows what tree and config were used to trigger the report,
then why:
> Let's maybe try it this way:
>
> #syz test: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
> 13e3c7793e2f
do you have to repeat that again in order for it to test something?
Powered by blists - more mailing lists