On Mon, 29 Aug 2022 at 16:19, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > 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@xxxxxx> > > 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 Agree. Looking at: $ git log --oneline fs/ext4/inline.c The following recent commit fixes a very similar failure mode: #syz fix: ext4: fix bug_on in ext4_writepages
