From: Peter Zijlstra <peterz@infradead•org>
To: syzbot <syzbot+b8e8c01c8ade4fe6e48f@syzkaller•appspotmail.com>
Cc: acme@kernel•org, alexander.shishkin@linux•intel.com,
bpf@vger•kernel.org, jolsa@kernel•org,
linux-kernel@vger•kernel.org, linux-perf-users@vger•kernel.org,
mark.rutland@arm•com, mingo@redhat•com, namhyung@kernel•org,
netdev@vger•kernel.org, syzkaller-bugs@googlegroups•com
Subject: Re: [syzbot] KASAN: use-after-free Read in put_pmu_ctx
Date: Tue, 20 Dec 2022 11:04:30 +0100 [thread overview]
Message-ID: <Y6GIrqpDU331TTeB@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <000000000000de0f0b05f03e6d9b@google.com>
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.
prev parent reply other threads:[~2022-12-20 10:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 8:04 [syzbot] KASAN: use-after-free Read in put_pmu_ctx syzbot
2022-12-19 14:40 ` Peter Zijlstra
2022-12-19 19:33 ` sdf
2022-12-19 19:56 ` syzbot
2022-12-19 21:33 ` sdf
2022-12-19 22:24 ` syzbot
2022-12-20 8:22 ` Peter Zijlstra
2022-12-20 17:10 ` Stanislav Fomichev
2022-12-20 19:37 ` syzbot
2022-12-21 2:42 ` Chengming Zhou
2022-12-22 20:59 ` Peter Zijlstra
2022-12-23 10:08 ` Chengming Zhou
2022-12-20 8:25 ` Peter Zijlstra
2022-12-20 8:43 ` syzbot
2022-12-20 10:04 ` Peter Zijlstra [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=Y6GIrqpDU331TTeB@hirez.programming.kicks-ass.net \
--to=peterz@infradead$(echo .)org \
--cc=acme@kernel$(echo .)org \
--cc=alexander.shishkin@linux$(echo .)intel.com \
--cc=bpf@vger$(echo .)kernel.org \
--cc=jolsa@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-perf-users@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=mingo@redhat$(echo .)com \
--cc=namhyung@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=syzbot+b8e8c01c8ade4fe6e48f@syzkaller$(echo .)appspotmail.com \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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