From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+8b376a77b2f364097fbe@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity check on sbi->total_valid_block_count
Date: Sat, 12 Apr 2025 17:11:05 +0000 [thread overview]
Message-ID: <174447786527.711489.2899173657997269764.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250408122208.2297777-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 8 Apr 2025 20:22:08 +0800 you wrote:
> syzbot reported a f2fs bug as below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/f2fs.h:2521!
> RIP: 0010:dec_valid_block_count+0x3b2/0x3c0 fs/f2fs/f2fs.h:2521
> Call Trace:
> f2fs_truncate_data_blocks_range+0xc8c/0x11a0 fs/f2fs/file.c:695
> truncate_dnode+0x417/0x740 fs/f2fs/node.c:973
> truncate_nodes+0x3ec/0xf50 fs/f2fs/node.c:1014
> f2fs_truncate_inode_blocks+0x8e3/0x1370 fs/f2fs/node.c:1197
> f2fs_do_truncate_blocks+0x840/0x12b0 fs/f2fs/file.c:810
> f2fs_truncate_blocks+0x10d/0x300 fs/f2fs/file.c:838
> f2fs_truncate+0x417/0x720 fs/f2fs/file.c:888
> f2fs_setattr+0xc4f/0x12f0 fs/f2fs/file.c:1112
> notify_change+0xbca/0xe90 fs/attr.c:552
> do_truncate+0x222/0x310 fs/open.c:65
> handle_truncate fs/namei.c:3466 [inline]
> do_open fs/namei.c:3849 [inline]
> path_openat+0x2e4f/0x35d0 fs/namei.c:4004
> do_filp_open+0x284/0x4e0 fs/namei.c:4031
> do_sys_openat2+0x12b/0x1d0 fs/open.c:1429
> do_sys_open fs/open.c:1444 [inline]
> __do_sys_creat fs/open.c:1522 [inline]
> __se_sys_creat fs/open.c:1516 [inline]
> __x64_sys_creat+0x124/0x170 fs/open.c:1516
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to do sanity check on sbi->total_valid_block_count
https://git.kernel.org/jaegeuk/f2fs/c/05872a167c2c
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:[~2025-04-12 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 12:22 Chao Yu
2025-04-12 17:11 ` 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=174447786527.711489.2899173657997269764.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+8b376a77b2f364097fbe@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
Powered by JetHome