linux-ext4 - Re: [syzbot] [ext4?] INFO: task hung in ext4_evict_ea

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+ZvEjpX8a9VW4tS1YSP8RE6xjb8C9ae6PcSa0rr-q+62g@mail.gmail.com>
Date: Mon, 16 Sep 2024 15:28:33 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Bart Van Assche <bvanassche@....org>
Cc: 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, syzkaller <syzkaller@...glegroups.com>
Subject: Re: [syzbot] [ext4?] INFO: task hung in ext4_evict_ea_inode

On Fri, 3 Feb 2023 at 19:11, Bart Van Assche <bvanassche@....org> wrote:
>
> 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.

Hi Bart,

syzbot has logic to detect commits that don't affect builds.
It hashes SHF_ALLOC vmlinux sections to check if the commit actually
has any effect on the binary:
https://github.com/google/syzkaller/blob/c673ca06b23cea94091ab496ef62c3513e434585/pkg/build/linux.go#L253-L286

Bug CONFIG_UFS_FS is enabled on syzbot, it has some coverage for it,
and strings affect the binary (can actually be the root cause for
bugs). So I don't see what else can be done here automatically.