From: syzbot <syzbot+b8e8c01c8ade4fe6e48f@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in put_pmu_ctx
Date: Mon, 19 Dec 2022 05:15:23 -0800 [thread overview]
Message-ID: <000000000000a473b905f02e1c4d@google.com> (raw)
In-Reply-To: <20221219124321.1504-1-hdanton@sina.com>
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: { P5552 } 2685 jiffies s: 2817 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: f9ff5644 Merge tag 'hsi-for-6.2' of git://git.kernel.o..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1337f01b880000
kernel config: https://syzkaller.appspot.com/x/.config?x=3263313469e7ca77
dashboard link: https://syzkaller.appspot.com/bug?extid=b8e8c01c8ade4fe6e48f
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=10acb79d880000
next parent reply other threads:[~2022-12-19 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221219124321.1504-1-hdanton@sina.com>
2022-12-19 13:15 ` syzbot [this message]
[not found] <20221219100606.1438-1-hdanton@sina.com>
2022-12-19 10:40 ` [syzbot] KASAN: use-after-free Read in put_pmu_ctx syzbot
2022-12-19 8:04 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
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=000000000000a473b905f02e1c4d@google.com \
--to=syzbot+b8e8c01c8ade4fe6e48f@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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