[Android 5.10] kernel BUG in ext4_mb_load_buddy_gfp

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3ad342cf5b2c Revert "net: mdio: fix owner field for mdio b..
git tree: android13-5.10-lts
console+strace: https://syzkaller.appspot.com/x/log.txt?x=1779ec6c280000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c2e555eed123787
dashboard link: https://syzkaller.appspot.com/bug?extid=da70412187f83135ac70
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=11f7edf2280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=179ae304280000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/68efc541dcd2/disk-3ad342cf.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f1c55bff052a/vmlinux-3ad342cf.xz
kernel image: https://storage.googleapis.com/syzbot-assets/62b39d17209d/bzImage-3ad342cf.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/32029579273a/mount_0.gz

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

------------[ cut here ]------------
kernel BUG at fs/ext4/ext4.h:3247!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 289 Comm: syz-executor968 Not tainted 5.10.177-syzkaller #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:3247 [inline]
RIP: 0010:ext4_mb_load_buddy_gfp+0xf5d/0x1020 fs/ext4/mballoc.c:1174
Code: ff e8 47 3c c8 ff e9 f0 f2 ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 52 f3 ff ff e8 4d 3c c8 ff e9 48 f3 ff ff e8 83 2e 8b ff <0f> 0b e9 62 00 00 00 e8 77 2e 8b ff e9 ef fb ff ff e9 65 00 00 00
RSP: 0018:ffffc90000b17a30 EFLAGS: 00010293
RAX: ffffffff81df3e6d RBX: 00000000fffff171 RCX: ffff88811d9e13c0
RDX: 0000000000000000 RSI: 00000000fffff171 RDI: 0000000000000001
RBP: ffffc90000b17ab0 R08: ffffffff81df2ffc R09: ffffed1021faf090
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff88811e694000 R14: 1ffff11023cd2679 R15: ffff88811e6933c8
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fabd0378a08 CR3: 000000000660f000 CR4: 00000000003506b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_discard_preallocations+0x79c/0xef0 fs/ext4/mballoc.c:4451
ext4_release_file+0x16e/0x310 fs/ext4/file.c:152
__fput+0x309/0x760 fs/file_table.c:281
____fput+0x15/0x20 fs/file_table.c:314
task_work_run+0x129/0x190 kernel/task_work.c:164
exit_task_work include/linux/task_work.h:32 [inline]
do_exit+0xc83/0x2a50 kernel/exit.c:861
do_group_exit+0x141/0x310 kernel/exit.c:983
__do_sys_exit_group kernel/exit.c:994 [inline]
__se_sys_exit_group kernel/exit.c:992 [inline]
__x64_sys_exit_group+0x3f/0x40 kernel/exit.c:992
do_syscall_64+0x34/0x70
entry_SYSCALL_64_after_hwframe+0x61/0xc6
RIP: 0033:0x7fabd0334819
Code: Unable to access opcode bytes at RIP 0x7fabd03347ef.
RSP: 002b:00007ffd0d85bef8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007fabd03a9370 RCX: 00007fabd0334819
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffffffffffc0 R09: 0000000000000000
R10: 000000000001ffff R11: 0000000000000246 R12: 00007fabd03a9370
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
Modules linked in:
---[ end trace b578b9d4114da835 ]---
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:3247 [inline]
RIP: 0010:ext4_mb_load_buddy_gfp+0xf5d/0x1020 fs/ext4/mballoc.c:1174
Code: ff e8 47 3c c8 ff e9 f0 f2 ff ff 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c 52 f3 ff ff e8 4d 3c c8 ff e9 48 f3 ff ff e8 83 2e 8b ff <0f> 0b e9 62 00 00 00 e8 77 2e 8b ff e9 ef fb ff ff e9 65 00 00 00
RSP: 0018:ffffc90000b17a30 EFLAGS: 00010293
RAX: ffffffff81df3e6d RBX: 00000000fffff171 RCX: ffff88811d9e13c0
RDX: 0000000000000000 RSI: 00000000fffff171 RDI: 0000000000000001
RBP: ffffc90000b17ab0 R08: ffffffff81df2ffc R09: ffffed1021faf090
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff88811e694000 R14: 1ffff11023cd2679 R15: ffff88811e6933c8
FS: 0000000000000000(0000) GS:ffff8881f7000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fabd0378a08 CR3: 000000000660f000 CR4: 00000000003506b0
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