[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8e13233a-2eb6-6d92-e94f-b94db8b518ed@acm.org>
Date: Fri, 3 Feb 2023 10:07:17 -0800
From: Bart Van Assche <bvanassche@....org>
To: syzbot <syzbot+38e6635a03c83c76297a@...kaller.appspotmail.com>,
adilger.kernel@...ger.ca, alim.akhtar@...sung.com,
avri.altman@....com, beanhuo@...ron.com, hdanton@...a.com,
jejb@...ux.ibm.com, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
martin.petersen@...cle.com, syzkaller-bugs@...glegroups.com,
tytso@....edu, wsa+renesas@...g-engineering.com
Subject: Re: [syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode
On 2/3/23 00:53, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 82ede9c19839079e7953a47895729852a440080c
> Author: Wolfram Sang <wsa+renesas@...g-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.
Powered by blists - more mailing lists