From: syzbot <syzbot+fa603ae6b02658401ca7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tristmd@gmail.com
Subject: Re: [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbJoin (2)
Date: Fri, 17 Apr 2026 10:25:03 -0700 [thread overview]
Message-ID: <69e26cef.a00a0220.1bd0ca.0013.GAE@google.com> (raw)
In-Reply-To: <177644279532.3785498.3765237981283024847@talencesecurity.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
UBSAN: shift-out-of-bounds in dbJoin
------------[ cut here ]------------
UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:2885:11
shift exponent 132 is too large for 32-bit type 'int'
CPU: 0 UID: 0 PID: 128 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
ubsan_epilogue+0xa/0x30 lib/ubsan.c:233
__ubsan_handle_shift_out_of_bounds+0x385/0x410 lib/ubsan.c:494
dbJoin+0x34f/0x380 fs/jfs/jfs_dmap.c:2885
dbFreeBits+0x4e1/0xdb0 fs/jfs/jfs_dmap.c:2427
dbFreeDmap fs/jfs/jfs_dmap.c:2176 [inline]
dbFree+0x336/0x650 fs/jfs/jfs_dmap.c:485
txFreeMap+0x7ff/0xde0 fs/jfs/jfs_txnmgr.c:2536
txUpdateMap+0x308/0x9c0 fs/jfs/jfs_txnmgr.c:-1
txLazyCommit fs/jfs/jfs_txnmgr.c:2666 [inline]
jfs_lazycommit+0x3ef/0xa10 fs/jfs/jfs_txnmgr.c:2735
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
---[ end trace ]---
Kernel panic - not syncing: UBSAN: panic_on_warn set ...
CPU: 0 UID: 0 PID: 128 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/18/2026
Call Trace:
<TASK>
vpanic+0x56c/0xa60 kernel/panic.c:650
panic+0xc5/0xd0 kernel/panic.c:787
check_panic_on_warn+0x89/0xb0 kernel/panic.c:524
__ubsan_handle_shift_out_of_bounds+0x385/0x410 lib/ubsan.c:494
dbJoin+0x34f/0x380 fs/jfs/jfs_dmap.c:2885
dbFreeBits+0x4e1/0xdb0 fs/jfs/jfs_dmap.c:2427
dbFreeDmap fs/jfs/jfs_dmap.c:2176 [inline]
dbFree+0x336/0x650 fs/jfs/jfs_dmap.c:485
txFreeMap+0x7ff/0xde0 fs/jfs/jfs_txnmgr.c:2536
txUpdateMap+0x308/0x9c0 fs/jfs/jfs_txnmgr.c:-1
txLazyCommit fs/jfs/jfs_txnmgr.c:2666 [inline]
jfs_lazycommit+0x3ef/0xa10 fs/jfs/jfs_txnmgr.c:2735
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Kernel Offset: disabled
Tested on:
commit: d730905b Merge tag 'mips_7.1' of git://git.kernel.org/..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=16e2a4ce580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4bcfdf96e3f779b1
dashboard link: https://syzkaller.appspot.com/bug?extid=fa603ae6b02658401ca7
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=15ea1906580000
next parent reply other threads:[~2026-04-17 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <177644279532.3785498.3765237981283024847@talencesecurity.com>
2026-04-17 17:25 ` syzbot [this message]
[not found] <177645357028.264607.10148298597246523532@gmail.com>
2026-04-17 19:45 ` [syzbot] [jfs?] UBSAN: shift-out-of-bounds in dbJoin (2) syzbot
[not found] <20260417101156.2489265-1-tristmd@gmail.com>
2026-04-17 10:37 ` syzbot
2025-12-06 16:31 syzbot
2025-12-07 3:18 ` Edward Adam Davis
2025-12-07 3:52 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69e26cef.a00a0220.1bd0ca.0013.GAE@google.com \
--to=syzbot+fa603ae6b02658401ca7@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tristmd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox