From: syzbot <syzbot+9b69b8d10ab4a7d88056@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: corrupted list in p9_fd_cancel (2)
Date: Sun, 23 Oct 2022 21:22:24 -0700 [thread overview]
Message-ID: <00000000000076ee7c05ebc0238d@google.com> (raw)
In-Reply-To: <20221024012302.2611-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: { P4081 } 2640 jiffies s: 2857 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: aae703b0 Merge tag 'for-6.1-rc1-tag' 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=161be616880000
kernel config: https://syzkaller.appspot.com/x/.config?x=4789759e8a6d5f57
dashboard link: https://syzkaller.appspot.com/bug?extid=9b69b8d10ab4a7d88056
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
patch: https://syzkaller.appspot.com/x/patch.diff?x=153d373a880000
next parent reply other threads:[~2022-10-24 4:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221024012302.2611-1-hdanton@sina.com>
2022-10-24 4:22 ` syzbot [this message]
[not found] <20221024070414.2711-1-hdanton@sina.com>
2022-10-24 17:31 ` [syzbot] BUG: corrupted list in p9_fd_cancel (2) syzbot
[not found] <20221023135812.2493-1-hdanton@sina.com>
2022-10-23 16:08 ` syzbot
2022-10-23 10:41 syzbot
2022-10-23 16:09 ` Christian Schoenebeck
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=00000000000076ee7c05ebc0238d@google.com \
--to=syzbot+9b69b8d10ab4a7d88056@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;
as well as URLs for NNTP newsgroup(s).