From: syzbot <syzbot+007bfe0f3330f6e1e7d1@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] inconsistent lock state in sync_info_debugfs_show
Date: Sat, 19 Nov 2022 02:50:17 -0800 [thread overview]
Message-ID: <000000000000793ce105edd0969e@google.com> (raw)
In-Reply-To: <20221119095108.4564-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: { P4107 } 2631 jiffies s: 2805 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: 84368d88 Merge tag 'soc-fixes-6.1-3' of git://git.kern..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=146d20fd880000
kernel config: https://syzkaller.appspot.com/x/.config?x=6f4e5e9899396248
dashboard link: https://syzkaller.appspot.com/bug?extid=007bfe0f3330f6e1e7d1
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=120fe909880000
next parent reply other threads:[~2022-11-19 10:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221119095108.4564-1-hdanton@sina.com>
2022-11-19 10:50 ` syzbot [this message]
[not found] <20221119081011.4372-1-hdanton@sina.com>
2022-11-19 9:43 ` [syzbot] inconsistent lock state in sync_info_debugfs_show syzbot
2022-01-27 16:33 syzbot
2022-11-19 2:46 ` syzbot
2022-11-22 14:51 ` Daniel Vetter
2022-11-22 17:31 ` Christian König
2022-11-20 20:51 ` syzbot
2022-11-22 19:48 ` Daniel Vetter
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=000000000000793ce105edd0969e@google.com \
--to=syzbot+007bfe0f3330f6e1e7d1@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