[Android 6.1] kernel BUG in ext4_mb_load_buddy_gfp

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 10e4c804f2f9 ANDROID: GKI: add symbol list file for unisoc
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1717804a280000
kernel config: https://syzkaller.appspot.com/x/.config?x=69801444f67a0156
dashboard link: https://syzkaller.appspot.com/bug?extid=0c2e4af35c1c6787b863
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=14b3a5be280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12dedbbe280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/bebc792b5ce2/disk-10e4c804.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/670a309c75c1/vmlinux-10e4c804.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b56c49867e2f/bzImage-10e4c804.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/e39610644690/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ext4/ext4.h:3331!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 334 Comm: syz-executor217 Not tainted 6.1.25-syzkaller-00172-g10e4c804f2f9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:3331 [inline]
RIP: 0010:ext4_mb_load_buddy_gfp+0xef8/0xf10 fs/ext4/mballoc.c:1448
Code: ae 6f c6 ff e9 de f3 ff ff e8 f4 0c 81 ff 48 c7 c7 20 84 8b 86 4c 89 ee 48 89 da e8 52 32 a7 00 e9 50 f2 ff ff e8 d8 0c 81 ff <0f> 0b e8 d1 0c 81 ff 0f 0b e8 ca 0c 81 ff 0f 0b 0f 1f 84 00 00 00
RSP: 0018:ffffc90000fc75c8 EFLAGS: 00010293
RAX: ffffffff81f28bf8 RBX: 0000000000000001 RCX: ffff88810d19df00
RDX: 0000000000000000 RSI: 00000000ffffe69e RDI: 0000000000000001
RBP: ffffc90000fc7650 R08: ffffffff81f27dec R09: ffffed1022521bcb
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000ffffe69e
R13: ffff88810d2ae000 R14: ffff8881099353a8 R15: ffff888109935018
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020002004 CR3: 0000000120d08000 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:5021
ext4_release_file+0x16e/0x310 fs/ext4/file.c:166
__fput+0x3ab/0x870 fs/file_table.c:320
____fput+0x15/0x20 fs/file_table.c:348
task_work_run+0x24d/0x2e0 kernel/task_work.c:179
exit_task_work include/linux/task_work.h:38 [inline]
do_exit+0xbb0/0x2910 kernel/exit.c:870
do_group_exit+0x21a/0x2d0 kernel/exit.c:1020
get_signal+0x169d/0x1820 kernel/signal.c:2858
arch_do_signal_or_restart+0xb0/0x16f0 arch/x86/kernel/signal.c:869
exit_to_user_mode_loop+0x6b/0xa0 kernel/entry/common.c:168
exit_to_user_mode_prepare+0x5a/0xa0 kernel/entry/common.c:204
__syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
syscall_exit_to_user_mode+0x26/0x130 kernel/entry/common.c:297
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f341af194d9
Code: Unable to access opcode bytes at 0x7f341af194af.
RSP: 002b:00007f3412b242f8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007f341af9e7b0 RCX: 00007f341af194d9
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007f341af9e7b8
RBP: 00007f341af6bc38 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f341af6b6a0
R13: 0030656c69662f2e R14: 6f6f6c2f7665642f R15: 00007f341af9e7b8
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:3331 [inline]
RIP: 0010:ext4_mb_load_buddy_gfp+0xef8/0xf10 fs/ext4/mballoc.c:1448
Code: ae 6f c6 ff e9 de f3 ff ff e8 f4 0c 81 ff 48 c7 c7 20 84 8b 86 4c 89 ee 48 89 da e8 52 32 a7 00 e9 50 f2 ff ff e8 d8 0c 81 ff <0f> 0b e8 d1 0c 81 ff 0f 0b e8 ca 0c 81 ff 0f 0b 0f 1f 84 00 00 00
RSP: 0018:ffffc90000fc75c8 EFLAGS: 00010293
RAX: ffffffff81f28bf8 RBX: 0000000000000001 RCX: ffff88810d19df00
RDX: 0000000000000000 RSI: 00000000ffffe69e RDI: 0000000000000001
RBP: ffffc90000fc7650 R08: ffffffff81f27dec R09: ffffed1022521bcb
R10: 0000000000000000 R11: dffffc0000000001 R12: 00000000ffffe69e
R13: ffff88810d2ae000 R14: ffff8881099353a8 R15: ffff888109935018
FS: 0000000000000000(0000) GS:ffff8881f7100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055555735c5e8 CR3: 00000001229af000 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 b4319e457d6e3fb33e443efeaf4634fc36e8a9ed
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=17aeb358e80000
start commit: 5e7421101fe2 ANDROID: ABI: Update symbol for Exynos SoC
git tree: android14-6.1
kernel config: https://syzkaller.appspot.com/x/.config?x=b75c7b7ab5a09aff
dashboard link: https://syzkaller.appspot.com/bug?extid=0c2e4af35c1c6787b863
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15da2bb4a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=137c810aa80000

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

[syzbot]

Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.