From: syzbot <syzbot+38e6635a03c83c76297a@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode
Date: Wed, 11 Jan 2023 23:38:21 -0800 [thread overview]
Message-ID: <00000000000081b39405f20c338f@google.com> (raw)
In-Reply-To: <20230112033143.520-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: { P5530 } 2672 jiffies s: 2801 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: a689b938 Merge tag 'block-2023-01-06' of git://git.ker..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1687d102480000
kernel config: https://syzkaller.appspot.com/x/.config?x=33ad6720950f996d
dashboard link: https://syzkaller.appspot.com/bug?extid=38e6635a03c83c76297a
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=1157295a480000
next parent reply other threads:[~2023-01-12 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230112033143.520-1-hdanton@sina.com>
2023-01-12 7:38 ` syzbot [this message]
2023-01-11 13:40 [syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode syzbot
2023-02-03 8:53 ` syzbot
2023-02-03 18:07 ` Bart Van Assche
2024-09-16 13:28 ` Dmitry Vyukov
2024-09-16 13:41 ` Bart Van Assche
2024-09-16 13:55 ` Dmitry Vyukov
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=00000000000081b39405f20c338f@google.com \
--to=syzbot+38e6635a03c83c76297a@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.