From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+33379ce4ac76acf7d0c7@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity check on node blkaddr in truncate_node()
Date: Mon, 28 Oct 2024 17:40:47 +0000 [thread overview]
Message-ID: <173013724745.126843.2488678512223387224.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241016081337.598979-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 16 Oct 2024 16:13:37 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:2534!
> RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534
> Call Trace:
> truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909
> f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288
> f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856
> evict+0x4e8/0x9b0 fs/inode.c:723
> f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986
> f2fs_create+0x357/0x530 fs/f2fs/namei.c:394
> lookup_open fs/namei.c:3595 [inline]
> open_last_lookups fs/namei.c:3694 [inline]
> path_openat+0x1c03/0x3590 fs/namei.c:3930
> do_filp_open+0x235/0x490 fs/namei.c:3960
> do_sys_openat2+0x13e/0x1d0 fs/open.c:1415
> do_sys_open fs/open.c:1430 [inline]
> __do_sys_openat fs/open.c:1446 [inline]
> __se_sys_openat fs/open.c:1441 [inline]
> __x64_sys_openat+0x247/0x2a0 fs/open.c:1441
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to do sanity check on node blkaddr in truncate_node()
https://git.kernel.org/jaegeuk/f2fs/c/e767ae13e67d
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:[~2024-10-28 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:13 [PATCH] f2fs: fix to do sanity check on node blkaddr in truncate_node() Chao Yu
2024-10-28 17:40 ` 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=173013724745.126843.2488678512223387224.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=stable@vger.kernel.org \
--cc=syzbot+33379ce4ac76acf7d0c7@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