From: Bart Van Assche <bvanassche@acm.org>
To: syzbot <syzbot+38e6635a03c83c76297a@syzkaller.appspotmail.com>,
adilger.kernel@dilger.ca, alim.akhtar@samsung.com,
avri.altman@wdc.com, beanhuo@micron.com, hdanton@sina.com,
jejb@linux.ibm.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, wsa+renesas@sang-engineering.com
Subject: Re: [syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode
Date: Fri, 3 Feb 2023 10:07:17 -0800 [thread overview]
Message-ID: <8e13233a-2eb6-6d92-e94f-b94db8b518ed@acm.org> (raw)
In-Reply-To: <00000000000039fb2d05f3c7d0ed@google.com>
On 2/3/23 00:53, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 82ede9c19839079e7953a47895729852a440080c
> Author: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Date: Tue Jun 21 14:46:53 2022 +0000
>
> scsi: ufs: core: Fix typos in error messages
To the syzbot maintainers: I think this is a good example of a bisection
result that is wrong. It is unlikely that fixing typos in kernel
messages would affect whether or not the kernel hangs. Additionally, as
far as I know, the systems used by syzbot (Google Compute Engine virtual
machines) do trigger any code in the UFS driver.
Bart.
next prev parent reply other threads:[~2023-02-03 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=8e13233a-2eb6-6d92-e94f-b94db8b518ed@acm.org \
--to=bvanassche@acm.org \
--cc=adilger.kernel@dilger.ca \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=hdanton@sina.com \
--cc=jejb@linux.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzbot+38e6635a03c83c76297a@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=wsa+renesas@sang-engineering.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).