================================================================================
UBSAN: Undefined behaviour in fs/jfs/jfs_mount.c:385:25
shift exponent 13324 is too large for 32-bit type 'int'
CPU: 0 PID: 13962 Comm: syz-executor.5 Not tainted 4.19.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x22c/0x33e lib/dump_stack.c:118
 ubsan_epilogue+0xe/0x3a lib/ubsan.c:161
 __ubsan_handle_shift_out_of_bounds.cold+0x1c4/0x250 lib/ubsan.c:422
 chkSuper.cold+0x1e/0x98 fs/jfs/jfs_mount.c:385
 jfs_mount+0x47/0x3d0 fs/jfs/jfs_mount.c:94
 jfs_fill_super+0x55c/0xb50 fs/jfs/super.c:589
 mount_bdev+0x2fc/0x3b0 fs/super.c:1158
 mount_fs+0xa3/0x318 fs/super.c:1261
 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
 vfs_kern_mount fs/namespace.c:951 [inline]
 do_new_mount fs/namespace.c:2469 [inline]
 do_mount+0x51c/0x2f10 fs/namespace.c:2799
 ksys_mount+0xcf/0x130 fs/namespace.c:3015
 __do_sys_mount fs/namespace.c:3029 [inline]
 __se_sys_mount fs/namespace.c:3026 [inline]
 __x64_sys_mount+0xba/0x150 fs/namespace.c:3026
 do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460bca
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 dd 87 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 ba 87 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f72f6ad7a88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f72f6ad7b20 RCX: 0000000000460bca
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 00007f72f6ad7ae0
RBP: 00007f72f6ad7ae0 R08: 00007f72f6ad7b20 R09: 00000000200000c0
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200000c0
R13: 0000000020000100 R14: 0000000020000200 R15: 000000002006d200
================================================================================
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
================================================================================
UBSAN: Undefined behaviour in fs/jfs/jfs_imap.c:458:7
shift exponent -13312 is negative
CPU: 0 PID: 13962 Comm: syz-executor.5 Not tainted 4.19.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x22c/0x33e lib/dump_stack.c:118
 ubsan_epilogue+0xe/0x3a lib/ubsan.c:161
 __ubsan_handle_shift_out_of_bounds.cold+0x1c4/0x250 lib/ubsan.c:422
 diReadSpecial.cold+0x1b/0x3e fs/jfs/jfs_imap.c:458
 jfs_mount+0x83/0x3d0 fs/jfs/jfs_mount.c:98
 jfs_fill_super+0x55c/0xb50 fs/jfs/super.c:589
 mount_bdev+0x2fc/0x3b0 fs/super.c:1158
 mount_fs+0xa3/0x318 fs/super.c:1261
 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
 vfs_kern_mount fs/namespace.c:951 [inline]
 do_new_mount fs/namespace.c:2469 [inline]
 do_mount+0x51c/0x2f10 fs/namespace.c:2799
 ksys_mount+0xcf/0x130 fs/namespace.c:3015
 __do_sys_mount fs/namespace.c:3029 [inline]
 __se_sys_mount fs/namespace.c:3026 [inline]
 __x64_sys_mount+0xba/0x150 fs/namespace.c:3026
 do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460bca
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 dd 87 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 ba 87 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f72f6ad7a88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f72f6ad7b20 RCX: 0000000000460bca
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 00007f72f6ad7ae0
RBP: 00007f72f6ad7ae0 R08: 00007f72f6ad7b20 R09: 00000000200000c0
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200000c0
R13: 0000000020000100 R14: 0000000020000200 R15: 000000002006d200
================================================================================
================================================================================
UBSAN: Undefined behaviour in fs/jfs/jfs_imap.c:126:7
shift exponent -13312 is negative
CPU: 0 PID: 13962 Comm: syz-executor.5 Not tainted 4.19.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x22c/0x33e lib/dump_stack.c:118
 ubsan_epilogue+0xe/0x3a lib/ubsan.c:161
 __ubsan_handle_shift_out_of_bounds.cold+0x1c4/0x250 lib/ubsan.c:422
 diMount.cold+0x17/0x1c fs/jfs/jfs_imap.c:126
 jfs_mount+0xbf/0x3d0 fs/jfs/jfs_mount.c:111
 jfs_fill_super+0x55c/0xb50 fs/jfs/super.c:589
 mount_bdev+0x2fc/0x3b0 fs/super.c:1158
 mount_fs+0xa3/0x318 fs/super.c:1261
 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
 vfs_kern_mount fs/namespace.c:951 [inline]
 do_new_mount fs/namespace.c:2469 [inline]
 do_mount+0x51c/0x2f10 fs/namespace.c:2799
 ksys_mount+0xcf/0x130 fs/namespace.c:3015
 __do_sys_mount fs/namespace.c:3029 [inline]
 __se_sys_mount fs/namespace.c:3026 [inline]
 __x64_sys_mount+0xba/0x150 fs/namespace.c:3026
 do_syscall_64+0xf9/0x670 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x460bca
Code: b8 a6 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 dd 87 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 0f 83 ba 87 fb ff c3 66 0f 1f 84 00 00 00 00 00
RSP: 002b:00007f72f6ad7a88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f72f6ad7b20 RCX: 0000000000460bca
RDX: 00000000200000c0 RSI: 0000000020000100 RDI: 00007f72f6ad7ae0
RBP: 00007f72f6ad7ae0 R08: 00007f72f6ad7b20 R09: 00000000200000c0
R10: 0000000000000000 R11: 0000000000000202 R12: 00000000200000c0
R13: 0000000020000100 R14: 0000000020000200 R15: 000000002006d200
================================================================================
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=13998 comm=syz-executor.4
FAT-fs (loop0): bogus number of reserved sectors
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14045 comm=syz-executor.4
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14077 comm=syz-executor.4
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14122 comm=syz-executor.4
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14152 comm=syz-executor.4
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14179 comm=syz-executor.4
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.4'.
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14211 comm=syz-executor.4
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14232 comm=syz-executor.4
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14251 comm=syz-executor.4
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14272 comm=syz-executor.4
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
FAT-fs (loop0): bogus number of reserved sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
FAT-fs (loop0): invalid media value (0x00)
FAT-fs (loop0): Can't find a valid FAT filesystem
FAT-fs (loop0): invalid media value (0x00)
FAT-fs (loop0): Can't find a valid FAT filesystem
FAT-fs (loop0): invalid media value (0x00)
FAT-fs (loop0): Can't find a valid FAT filesystem
FAT-fs (loop0): invalid media value (0x00)
FAT-fs (loop0): Can't find a valid FAT filesystem
FAT-fs (loop0): invalid media value (0x00)
FAT-fs (loop0): Can't find a valid FAT filesystem
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14457 comm=syz-executor.4
FAT-fs (loop0): invalid media value (0x00)
FAT-fs (loop0): Can't find a valid FAT filesystem
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14491 comm=syz-executor.4
FAT-fs (loop0): bogus number of FAT sectors
ldm_validate_privheads(): Disk read failed.
 loop2: p1 p2[DM] p3[EZD] p4
FAT-fs (loop0): Can't find a valid FAT filesystem
loop2: partition table partially beyond EOD, truncated
loop2: p1 start 10 is beyond EOD, truncated
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
loop2: p2 start 25 is beyond EOD, truncated
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14513 comm=syz-executor.4
loop2: p3 start 10 is beyond EOD, truncated
loop2: p4 start 3976200192 is beyond EOD, truncated
FAT-fs (loop0): bogus number of FAT sectors
FAT-fs (loop0): Can't find a valid FAT filesystem
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14530 comm=syz-executor.4
FAT-fs (loop0): bogus number of FAT sectors
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
FAT-fs (loop0): Can't find a valid FAT filesystem
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14558 comm=syz-executor.4
netlink: 24 bytes leftover after parsing attributes in process `syz-executor.2'.
netlink: 40 bytes leftover after parsing attributes in process `syz-executor.4'.
SELinux: unrecognized netlink message: protocol=0 nlmsg_type=0 sclass=netlink_route_socket pid=14582 comm=syz-executor.4