linux-kernel - Re: [PATCH -next] ext4: Fix warning in ext4_da_release

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 for Android: free password hash cracker in your pocket

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

Message-ID: <YpDsiCTi8sidvO7X@mit.edu>
Date:   Fri, 27 May 2022 11:21:44 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     yebin <yebin10@...wei.com>
Cc:     Eric Whitney <enwlinux@...il.com>, adilger.kernel@...ger.ca,
        linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
        jack@...e.cz
Subject: Re: [PATCH -next] ext4: Fix warning in ext4_da_release_space

On Fri, May 27, 2022 at 05:10:43PM +0800, yebin wrote:
> 
> Maybe  you can  run syzkaller with log as follows :

Oh, so this was something that was found using Syzkaller.  Was this
using the public syzkaller; if so, can you provide a link the
Syzkaller report?

If this was a from privately run syzkaller instance, was there a C
reproducer?  It appears that this was from a fuzzed instance, and it's
painful enoguh to extract the file system image from the C reproducer.
I have no idea how to extract the file system image from a Syzkaller
reproducer.

In any case, it sounds like this was triggered from a maliciously
corrupted / fuzzed image.  Can this warning be triggered from a
consistent file system, or does it require a corrupted extent tree?

	   		   	   	   - Ted