Hello,
syzbot found the following issue on:
HEAD commit: fa3df276cd36 Linux 5.15.155
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16980c53180000
kernel config:
https://syzkaller.appspot.com/x/.config?x=f12ea3f162537c9c
dashboard link:
https://syzkaller.appspot.com/bug?extid=eac84ce8b38992ca3441
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/feaf3fb3f68f/disk-fa3df276.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/537c519f1dd0/vmlinux-fa3df276.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/5396ec75d1be/bzImage-fa3df276.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+eac84c...@syzkaller.appspotmail.com
================================================================================
UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:2707:11
shift exponent 80 is too large for 32-bit type 'int'
CPU: 1 PID: 5547 Comm: syz-executor.3 Not tainted 5.15.155-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2d0 lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_shift_out_of_bounds+0x3bf/0x420 lib/ubsan.c:321
dbSplit+0x21a/0x220 fs/jfs/jfs_dmap.c:2707
dbAllocBits+0x4e5/0x9a0 fs/jfs/jfs_dmap.c:2259
dbAllocDmap fs/jfs/jfs_dmap.c:2100 [inline]
dbAllocDmapLev+0x24c/0x490 fs/jfs/jfs_dmap.c:2054
dbAllocCtl+0x113/0x920 fs/jfs/jfs_dmap.c:1891
dbAllocAG+0x28b/0x10b0 fs/jfs/jfs_dmap.c:1432
dbAlloc+0x654/0xc90 fs/jfs/jfs_dmap.c:888
dtSplitUp fs/jfs/jfs_dtree.c:979 [inline]
dtInsert+0xda3/0x6b00 fs/jfs/jfs_dtree.c:868
jfs_symlink+0x823/0x10e0 fs/jfs/namei.c:1019
vfs_symlink+0x247/0x3d0 fs/namei.c:4429
do_symlinkat+0x1fd/0x600 fs/namei.c:4458
__do_sys_symlinkat fs/namei.c:4475 [inline]
__se_sys_symlinkat fs/namei.c:4472 [inline]
__x64_sys_symlinkat+0x95/0xa0 fs/namei.c:4472
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f31fff7ce69
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f31fe4ef0c8 EFLAGS: 00000246 ORIG_RAX: 000000000000010a
RAX: ffffffffffffffda RBX: 00007f32000aaf80 RCX: 00007f31fff7ce69
RDX: 0000000020000340 RSI: 0000000000000004 RDI: 0000000020000440
RBP: 00007f31fffc947a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f32000aaf80 R15: 00007ffd2cf46258
</TASK>
================================================================================
---
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 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