From: syzbot <syzbot+411debe54d318eaed386@syzkaller.appspotmail.com>
To: jfs-discussion@lists.sourceforge.net,
linux-kernel@vger.kernel.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] UBSAN: shift-out-of-bounds in dbJoin
Date: Mon, 10 Oct 2022 00:16:43 -0700 [thread overview]
Message-ID: <0000000000000bef6205eaa8f181@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 62e6e5940c0c Merge tag 'scsi-misc' of git://git.kernel.org..
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=16347cc8880000
kernel config: https://syzkaller.appspot.com/x/.config?x=4c13637ccca17699
dashboard link: https://syzkaller.appspot.com/bug?extid=411debe54d318eaed386
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1768f51c880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=175885cc880000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b4f4f04cf38f/disk-62e6e594.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dfb013b64867/vmlinux-62e6e594.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/64992a1b07af/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+411debe54d318eaed386@syzkaller.appspotmail.com
================================================================================
UBSAN: shift-out-of-bounds in fs/jfs/jfs_dmap.c:2760:11
shift exponent 78 is too large for 32-bit type 'int'
CPU: 1 PID: 122 Comm: jfsCommit Not tainted 6.0.0-syzkaller-07362-g62e6e5940c0c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106
ubsan_epilogue lib/ubsan.c:151 [inline]
__ubsan_handle_shift_out_of_bounds+0x33d/0x3b0 lib/ubsan.c:322
dbJoin+0x2e4/0x2f0 fs/jfs/jfs_dmap.c:2760
dbAdjCtl+0x3b1/0x9c0 fs/jfs/jfs_dmap.c:2500
dbFreeDmap fs/jfs/jfs_dmap.c:2064 [inline]
dbFree+0x3c6/0x660 fs/jfs/jfs_dmap.c:379
txFreeMap+0x97c/0xd70 fs/jfs/jfs_txnmgr.c:2510
xtTruncate+0xe74/0x32d0 fs/jfs/jfs_xtree.c:2467
jfs_free_zero_link+0x3f5/0x680 fs/jfs/namei.c:758
jfs_evict_inode+0x35a/0x440 fs/jfs/inode.c:153
evict+0x2a4/0x620 fs/inode.c:664
txUpdateMap+0x8eb/0xaa0 fs/jfs/jfs_txnmgr.c:2362
txLazyCommit fs/jfs/jfs_txnmgr.c:2659 [inline]
jfs_lazycommit+0x433/0xba0 fs/jfs/jfs_txnmgr.c:2727
kthread+0x266/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306
</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 syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2022-10-10 7:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=0000000000000bef6205eaa8f181@google.com \
--to=syzbot+411debe54d318eaed386@syzkaller.appspotmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzkaller-bugs@googlegroups.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