[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y6GIrqpDU331TTeB@hirez.programming.kicks-ass.net>
Date: Tue, 20 Dec 2022 11:04:30 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: syzbot <syzbot+b8e8c01c8ade4fe6e48f@...kaller.appspotmail.com>
Cc: 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 Tue, Dec 20, 2022 at 12:43:25AM -0800, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> INFO: rcu detected stall in corrupted
>
> rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P5791 } 2673 jiffies s: 2805 root: 0x0/T
> rcu: blocking rcu_node structures (internal RCU debug):
That is an entirely different issue methinks. Let me go write up a
Changelog for that thing and stuff it somewhere /urgent.
Powered by blists - more mailing lists