[Android 5.4] kernel BUG in ext4_trim_fs

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6d5c2c1877e5 UPSTREAM: usb: gadget: udc: renesas_usb3: Fix..
git tree: android12-5.4
console+strace: https://syzkaller.appspot.com/x/log.txt?x=103e9274a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fd5c1dc5dbc9ccb1
dashboard link: https://syzkaller.appspot.com/bug?extid=7c8d30c5e1c4731ea312
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=1367ddf8a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=160a326ca80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e9d240723b03/disk-6d5c2c18.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8d9c23a9a09e/vmlinux-6d5c2c18.xz
kernel image: https://storage.googleapis.com/syzbot-assets/de3e2d881bec/bzImage-6d5c2c18.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/8f40a4e897c8/mount_0.gz

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

ext4 filesystem being mounted at /root/file1 supports timestamps until 2038 (0x7fffffff)
------------[ cut here ]------------
kernel BUG at fs/ext4/ext4.h:2981!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 358 Comm: syz-executor108 Not tainted 5.4.242-syzkaller-00020-g6d5c2c1877e5 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:2981 [inline]
RIP: 0010:ext4_trim_fs+0x19b2/0x19c0 fs/ext4/mballoc.c:5325
Code: cf c8 ff e9 44 ec ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 33 fd ff ff 48 89 df e8 28 d0 c8 ff e9 26 fd ff ff e8 8e 15 99 ff <0f> 0b e8 77 d6 6f ff e8 82 15 99 ff 0f 0b 55 41 57 41 56 41 55 41
RSP: 0018:ffff8881dcbe7520 EFLAGS: 00010293
RAX: ffffffff81cb1532 RBX: 0000000000000001 RCX: ffff8881e2d43f00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: ffff8881dcbe7770 R08: ffffffff81cb02a8 R09: fffff94000ee00ff
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000001 R14: ffff8881dc042000 R15: ffff8881dc0463f0
FS: 0000555556ae4300(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200401bf CR3: 00000001e16b7000 CR4: 00000000003406b0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
ext4_ioctl+0x2168/0x3fd0 fs/ext4/ioctl.c:1125
do_vfs_ioctl+0x742/0x1720 fs/ioctl.c:47
ksys_ioctl fs/ioctl.c:742 [inline]
__do_sys_ioctl fs/ioctl.c:749 [inline]
__se_sys_ioctl fs/ioctl.c:747 [inline]
__x64_sys_ioctl+0xd4/0x110 fs/ioctl.c:747
do_syscall_64+0xca/0x1c0 arch/x86/entry/common.c:290
entry_SYSCALL_64_after_hwframe+0x5c/0xc1
Modules linked in:
---[ end trace c269d52e08e596c0 ]---
RIP: 0010:ext4_get_group_info fs/ext4/ext4.h:2981 [inline]
RIP: 0010:ext4_trim_fs+0x19b2/0x19c0 fs/ext4/mballoc.c:5325
Code: cf c8 ff e9 44 ec ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 33 fd ff ff 48 89 df e8 28 d0 c8 ff e9 26 fd ff ff e8 8e 15 99 ff <0f> 0b e8 77 d6 6f ff e8 82 15 99 ff 0f 0b 55 41 57 41 56 41 55 41
RSP: 0018:ffff8881dcbe7520 EFLAGS: 00010293
RAX: ffffffff81cb1532 RBX: 0000000000000001 RCX: ffff8881e2d43f00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: ffff8881dcbe7770 R08: ffffffff81cb02a8 R09: fffff94000ee00ff
R10: 0000000000000000 R11: dffffc0000000001 R12: dffffc0000000000
R13: 0000000000000001 R14: ffff8881dc042000 R15: ffff8881dc0463f0
FS: 0000555556ae4300(0000) GS:ffff8881f6e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000000200401bf CR3: 00000001e16b7000 CR4: 00000000003406b0
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