From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to set sbi->log_blocksize in advance
Date: Tue, 13 Oct 2026 22:30:39 +0000 [thread overview]
Message-ID: <179193063951.1493834.17396004482002929582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001000450.3822520-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 1 Oct 2026 00:04:50 +0000 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> syzbot reported a shift-out-of-bounds in __f2fs_commit_super():
>
> 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
> 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
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to set sbi->log_blocksize in advance
https://git.kernel.org/jaegeuk/f2fs/c/63bb030f36b8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 0:04 Chao Yu
2026-10-13 22:30 ` patchwork-bot+f2fs [this message]
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=179193063951.1493834.17396004482002929582.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+dfcbc1741488709db4b2@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®