From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: syzbot <syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.com>,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] UBSAN: shift-out-of-bounds in __f2fs_commit_super
Date: Wed, 30 Sep 2026 16:55:47 +0800 [thread overview]
Message-ID: <784ebcc3-2d37-4640-88fa-3385a646c2d5@kernel.org> (raw)
In-Reply-To: <6ab4ae74.80e1c6cc.1e8e5f.000c.GAE@google.com>
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
On 9/24/26 13:00, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: a8c591ed6b67 Add linux-next specific files for 20260922
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=16f98405580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=19be71c9d7429efd
> dashboard link: https://syzkaller.appspot.com/bug?extid=dfcbc1741488709db4b2
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11f98405580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=148ea515580000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/08a28cd722c6/disk-a8c591ed.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/e1c983b28f94/vmlinux-a8c591ed.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/ff7b15260591/bzImage-a8c591ed.xz
> mounted in repro: https://storage.googleapis.com/syzbot-assets/3e937ffb1f11/mount_0.gz
> fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=16029405580000)
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.com
>
> loop0: detected capacity change from 0 to 40427
> ------------[ cut here ]------------
> UBSAN: shift-out-of-bounds in fs/f2fs/super.c:3950:27
> shift exponent 4294967287 is too large for 64-bit type 'sector_t' (aka 'unsigned long long')
> CPU: 1 UID: 0 PID: 5622 Comm: syz-executor329 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/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+0x36d/0x400 lib/ubsan.c:494
> __f2fs_commit_super+0x43e/0x4d0 fs/f2fs/super.c:3950
> sanity_check_area_boundary+0x7c5/0xe20 fs/f2fs/super.c:4040
> sanity_check_raw_super fs/f2fs/super.c:4215 [inline]
> read_raw_super_block fs/f2fs/super.c:4625 [inline]
> f2fs_fill_super+0x1920/0x7fa0 fs/f2fs/super.c:5160
> get_tree_bdev_flags+0x430/0x4f0 fs/super.c:1872
> vfs_get_tree+0x92/0x2a0 fs/super.c:1932
> fc_mount fs/namespace.c:1198 [inline]
> do_new_mount_fc fs/namespace.c:3772 [inline]
> do_new_mount+0x319/0xdc0 fs/namespace.c:3848
> do_mount fs/namespace.c:4181 [inline]
> __do_sys_mount fs/namespace.c:4394 [inline]
> __se_sys_mount+0x31d/0x420 fs/namespace.c:4371
> do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
> do_syscall_64+0x166/0x520 arch/x86/entry/syscall_64.c:84
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f2eb02deeaa
> Code: 56 53 b8 9d 00 00 00 0f 05 83 f8 ea 75 a2 c7 05 e4 5b 09 00 00 00 00 00 eb 96 e8 51 05 00 00 90 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 d8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007ffcaf01ba78 EFLAGS: 00000286 ORIG_RAX: 00000000000000a5
> RAX: ffffffffffffffda RBX: 00007ffcaf01ba90 RCX: 00007f2eb02deeaa
> RDX: 0000200000000080 RSI: 0000200000000000 RDI: 00007ffcaf01ba90
> RBP: 0000200000000000 R08: 00007ffcaf01bad0 R09: 0000000000000000
> R10: 0000000000200000 R11: 0000000000000286 R12: 0000200000000080
> R13: 00007ffcaf01bad0 R14: 0000000000000003 R15: 0000000000200000
> </TASK>
> ---[ end trace ]---
>
>
> ---
> 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.
>
> 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
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-09-30 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 5:00 [f2fs-dev] [syzbot] [f2fs?] UBSAN: shift-out-of-bounds in __f2fs_commit_super syzbot
2026-09-30 8:55 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-30 13:53 ` 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=784ebcc3-2d37-4640-88fa-3385a646c2d5@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.