[Android 5.15] kernel BUG in ext4_mb_load_buddy_gfp (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 19c0ed55a470 Merge 5.15.106 into android13-5.15-lts
git tree: android13-5.15-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=14b28870280000
kernel config: https://syzkaller.appspot.com/x/.config?x=e8bc8779358f24fb
dashboard link: https://syzkaller.appspot.com/bug?extid=5da507c37b1f940af8ba
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11221c46280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=172860dc280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/8ade0e897782/disk-19c0ed55.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/203011b1fd4d/vmlinux-19c0ed55.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7f39bb0b7ba9/bzImage-19c0ed55.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/de4a98c4b223/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5da507...@syzkaller.appspotmail.com

------------[ cut here ]------------
kernel BUG at fs/ext4/ext4.h:3355!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 309 Comm: syz-executor315 Not tainted 5.15.106-syzkaller-00249-g19c0ed55a470 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:3355 [inline]
RIP: 0010:ext4_mb_load_buddy_gfp+0xee5/0xf00 fs/ext4/mballoc.c:1498
Code: 11 0f c8 ff e9 0d f4 ff ff e8 87 c7 86 ff 48 c7 c7 80 81 a9 86 4c 89 fe 4c 89 f2 e8 05 93 9a 00 e9 87 f2 ff ff e8 6b c7 86 ff <0f> 0b e8 64 c7 86 ff 0f 0b e8 5d c7 86 ff 0f 0b 66 2e 0f 1f 84 00
RSP: 0000:ffffc90000a474a0 EFLAGS: 00010293
RAX: ffffffff81e92455 RBX: 00000000fffff01a RCX: ffff888117b113c0
RDX: 0000000000000000 RSI: 00000000fffff01a RDI: 0000000000000001
RBP: ffffc90000a47530 R08: ffffffff81e91684 R09: ffffed102125a952
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11021510279
R13: ffff88810a8813c8 R14: 0000000000000001 R15: ffff88810a0c4000
FS: 00007fdef4ec5700(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561755727188 CR3: 000000011fbc8000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
ext4_discard_preallocations+0x79c/0xef0 fs/ext4/mballoc.c:5033
ext4_release_file+0x16e/0x310 fs/ext4/file.c:151
__fput+0x3fe/0x910 fs/file_table.c:280
____fput+0x15/0x20 fs/file_table.c:308
task_work_run+0x129/0x190 kernel/task_work.c:164
ptrace_notify+0x29e/0x350 kernel/signal.c:2383
ptrace_event include/linux/ptrace.h:152 [inline]
do_exit+0x2123/0x2b60 kernel/exit.c:815
do_group_exit+0x141/0x310 kernel/exit.c:997
get_signal+0x7a3/0x1630 kernel/signal.c:2891
arch_do_signal_or_restart+0xbd/0x1680 arch/x86/kernel/signal.c:865
handle_signal_work kernel/entry/common.c:148 [inline]
exit_to_user_mode_loop+0xa0/0xe0 kernel/entry/common.c:172
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:208
irqentry_exit_to_user_mode+0x9/0x20 kernel/entry/common.c:314
irqentry_exit+0x12/0x40 kernel/entry/common.c:405
exc_page_fault+0x47a/0x830 arch/x86/mm/fault.c:1608
asm_exc_page_fault+0x27/0x30 arch/x86/include/asm/idtentry.h:568
RIP: 0033:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 002b:0000000020000473 EFLAGS: 00010217
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007fdef4f24bf9
RDX: 00007fdef4f24bf9 RSI: 0000000000000058 RDI: 00007fdef4ec5110
RBP: 00007fdef4fa4780 R08: 0000000000000000 R09: 00000000c0000000
R10: 00007fdef4ec5110 R11: 0000000000000246 R12: 00007fdef4fa478c
R13: 00007ffcae3418af R14: 00007fdef4ec5300 R15: 0000000000022000
</TASK>
Modules linked in:
---[ end trace bbdb54182f523b9c ]---
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:3355 [inline]
RIP: 0010:ext4_mb_load_buddy_gfp+0xee5/0xf00 fs/ext4/mballoc.c:1498
Code: 11 0f c8 ff e9 0d f4 ff ff e8 87 c7 86 ff 48 c7 c7 80 81 a9 86 4c 89 fe 4c 89 f2 e8 05 93 9a 00 e9 87 f2 ff ff e8 6b c7 86 ff <0f> 0b e8 64 c7 86 ff 0f 0b e8 5d c7 86 ff 0f 0b 66 2e 0f 1f 84 00
RSP: 0000:ffffc90000a474a0 EFLAGS: 00010293
RAX: ffffffff81e92455 RBX: 00000000fffff01a RCX: ffff888117b113c0
RDX: 0000000000000000 RSI: 00000000fffff01a RDI: 0000000000000001
RBP: ffffc90000a47530 R08: ffffffff81e91684 R09: ffffed102125a952
R10: 0000000000000000 R11: dffffc0000000001 R12: 1ffff11021510279
R13: ffff88810a8813c8 R14: 0000000000000001 R15: ffff88810a0c4000
FS: 00007fdef4ec5700(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005601546a30f8 CR3: 000000011fbc8000 CR4: 00000000003506a0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to change bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot suspects this issue was fixed by commit:

commit 620a3c28221bb219b81bc0bffd065cc187494302
Author: Theodore Ts'o <ty...@mit.edu>
Date: Sat Apr 29 04:06:28 2023 +0000

ext4: allow ext4_get_group_info() to fail

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13904553a80000
start commit: 19c0ed55a470 Merge 5.15.106 into android13-5.15-lts
git tree: android13-5.15-lts

kernel config: https://syzkaller.appspot.com/x/.config?x=e8bc8779358f24fb
dashboard link: https://syzkaller.appspot.com/bug?extid=5da507c37b1f940af8ba

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1624d8fc280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17e93e7e280000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: ext4: allow ext4_get_group_info() to fail

For information about bisection process see: https://goo.gl/tpsmEJ#bisection