From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+15669ec8c35ddf6c3d43@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid panic once fallocation fails for pinfile
Date: Wed, 12 Feb 2025 03:00:40 +0000 [thread overview]
Message-ID: <173932924049.82998.16364535718355132249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250211063657.405289-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 11 Feb 2025 14:36:57 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:2746!
> CPU: 0 UID: 0 PID: 5323 Comm: syz.0.0 Not tainted 6.13.0-rc2-syzkaller-00018-g7cb1b4663150 #0
> RIP: 0010:get_new_segment fs/f2fs/segment.c:2746 [inline]
> RIP: 0010:new_curseg+0x1f52/0x1f70 fs/f2fs/segment.c:2876
> Call Trace:
> <TASK>
> __allocate_new_segment+0x1ce/0x940 fs/f2fs/segment.c:3210
> f2fs_allocate_new_section fs/f2fs/segment.c:3224 [inline]
> f2fs_allocate_pinning_section+0xfa/0x4e0 fs/f2fs/segment.c:3238
> f2fs_expand_inode_data+0x696/0xca0 fs/f2fs/file.c:1830
> f2fs_fallocate+0x537/0xa10 fs/f2fs/file.c:1940
> vfs_fallocate+0x569/0x6e0 fs/open.c:327
> do_vfs_ioctl+0x258c/0x2e40 fs/ioctl.c:885
> __do_sys_ioctl fs/ioctl.c:904 [inline]
> __se_sys_ioctl+0x80/0x170 fs/ioctl.c:892
> 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
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid panic once fallocation fails for pinfile
https://git.kernel.org/jaegeuk/f2fs/c/48ea8b200414
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-02-12 3:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 6:36 Chao Yu
2025-02-12 3:00 ` 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=173932924049.82998.16364535718355132249.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+15669ec8c35ddf6c3d43@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®