From: syzbot <syzbot+2f73ed585f115e98aee8@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [exfat?] INFO: task hung in exfat_write_inode
Date: Wed, 20 Dec 2023 22:35:03 -0800 [thread overview]
Message-ID: <000000000000b64208060cff4cad@google.com> (raw)
In-Reply-To: <20231221061105.1471131-1-lizhi.xu@windriver.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: { P5341 } 2673 jiffies s: 2901 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
console output: https://syzkaller.appspot.com/x/log.txt?x=1555014ee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=1bf08f50e8fff9ad
dashboard link: https://syzkaller.appspot.com/bug?extid=2f73ed585f115e98aee8
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1056bb4ee80000
next prev parent reply other threads:[~2023-12-21 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 18:53 [syzbot] [exfat?] INFO: task hung in exfat_write_inode syzbot
2023-11-29 21:42 ` syzbot
2023-11-30 7:28 ` [syzbot] " syzbot
2023-11-30 7:55 ` syzbot
2023-11-30 8:43 ` syzbot
2023-12-21 4:50 ` Lizhi Xu
2023-12-21 5:18 ` [syzbot] [exfat?] INFO: " syzbot
2023-12-21 6:11 ` Lizhi Xu
2023-12-21 6:35 ` syzbot [this message]
[not found] <20231130072806.1240587-1-lizhi.xu@windriver.com>
2023-11-30 7:45 ` [syzbot] [exfat?] INFO: " syzbot
[not found] <20231130075546.1506719-1-lizhi.xu@windriver.com>
2023-11-30 8:26 ` syzbot
[not found] <20231130084311.2983367-1-lizhi.xu@windriver.com>
2023-11-30 9:04 ` syzbot
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=000000000000b64208060cff4cad@google.com \
--to=syzbot+2f73ed585f115e98aee8@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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