[Android 6.1] UBSAN: shift-out-of-bounds in parse_options

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: d6a513a78492 UPSTREAM: scsi: ufs: core: Perform read back ..
git tree: android14-6.1
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16aa30dd980000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a8fbfddff407fc2
dashboard link: https://syzkaller.appspot.com/bug?extid=561af80c4a21ada6cf3e
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15315e05980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1695fde5980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9bab63786987/disk-d6a513a7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f43727b97efe/vmlinux-d6a513a7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c71b5745e72a/bzImage-d6a513a7.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/cb4187e2bd0a/mount_0.gz

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

loop0: detected capacity change from 0 to 40427
================================================================================
UBSAN: shift-out-of-bounds in fs/f2fs/super.c:911:5
shift exponent 105 is too large for 64-bit type 'unsigned long'
CPU: 0 PID: 294 Comm: syz-executor290 Not tainted 6.1.90-syzkaller-00020-gd6a513a78492 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x151/0x1b7 lib/dump_stack.c:106
dump_stack+0x15/0x1c lib/dump_stack.c:113
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_shift_out_of_bounds+0x3e1/0x440 lib/ubsan.c:321
parse_options+0x4b90/0x4ba0 fs/f2fs/super.c:911
f2fs_fill_super+0x23bc/0x6dc0 fs/f2fs/super.c:4288
mount_bdev+0x282/0x3b0 fs/super.c:1434
f2fs_mount+0x34/0x40 fs/f2fs/super.c:4724
legacy_get_tree+0xf1/0x190 fs/fs_context.c:632
vfs_get_tree+0x88/0x290 fs/super.c:1564
do_new_mount+0x2ba/0xb30 fs/namespace.c:3051
path_mount+0x671/0x1070 fs/namespace.c:3381
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount+0x2c4/0x3b0 fs/namespace.c:3579
__x64_sys_mount+0xbf/0xd0 fs/namespace.c:3579
x64_sys_call+0x49d/0x9a0 arch/x86/include/generated/asm/syscalls_64.h:166
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f7fcd937cfa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 5e 04 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff8eff0578 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fff8eff0590 RCX: 00007f7fcd937cfa
RDX: 0000000020000040 RSI: 00000000200000c0 RDI: 00007fff8eff0590
RBP: 0000000000000004 R08: 00007fff8eff05d0 R09: 00000000000054fa
R10: 0000000000000000 R11: 0000000000000286 R12: 0000000000000000
R13: 00007fff8eff05d0 R14: 0000000000000003 R15: 00000000013bd7ef
</TASK>
================================================================================
F2FS-fs (loop0): Not support 2199023255552, larger than 256


---
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 report is already addressed, 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 overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

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

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