linux-ext4 - Re: [syzbot] kernel BUG at fs/ext4/inline.c:LINE!

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]

Date:   Mon, 29 Aug 2022 16:19:50 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     syzbot <syzbot+4faa160fa96bfba639f8@...kaller.appspotmail.com>
Cc:     adilger.kernel@...ger.ca, hch@....de, linux-ext4@...r.kernel.org,
        linux-kernel@...r.kernel.org, paulmck@...nel.org,
        phil@...lpotter.co.uk, syzkaller-bugs@...glegroups.com,
        tytso@....edu
Subject: Re: [syzbot] kernel BUG at fs/ext4/inline.c:LINE!

On Mon, Aug 29, 2022 at 05:17:13AM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
> 
> commit 1045a06724f322ed61f1ffb994427c7bdbe64647
> Author: Christoph Hellwig <hch@....de>
> Date:   Wed Jun 29 15:01:02 2022 +0000
> 
>     remove CONFIG_ANDROID
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=16ab0893080000
> start commit:   a8ad9a2434dc Merge tag 'efi-urgent-for-v5.16-2' of git://g..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=2ebd4b29568807bc
> dashboard link: https://syzkaller.appspot.com/bug?extid=4faa160fa96bfba639f8
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=114ae045b00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=1785e92bb00000
> 
> If the result looks correct, please mark the issue as fixed by replying with:
> 
> #syz fix: remove CONFIG_ANDROID
> 
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection

I really doubt that ext4 has anything to do with the removal of
CONFIG_ANDROID unless the problem here was some of the other crazy RCU
delay issues around this config option.  Glad it's gone...