From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@kernel.org,
linux-kernel@vger.kernel.org,
syzbot+24124df3170c3638b35f@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to avoid updating zero-sized extent in extent cache
Date: Tue, 11 Nov 2025 22:50:17 +0000 [thread overview]
Message-ID: <176290141749.3596344.15754105220634232444.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251020024213.332873-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 20 Oct 2025 10:42:12 +0800 you wrote:
> As syzbot reported:
>
> F2FS-fs (loop0): __update_extent_tree_range: extent len is zero, type: 0, extent [0, 0, 0], age [0, 0]
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/extent_cache.c:678!
> Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
> CPU: 0 UID: 0 PID: 5336 Comm: syz.0.0 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
> RIP: 0010:__update_extent_tree_range+0x13bc/0x1500 fs/f2fs/extent_cache.c:678
> Call Trace:
> <TASK>
> f2fs_update_read_extent_cache_range+0x192/0x3e0 fs/f2fs/extent_cache.c:1085
> f2fs_do_zero_range fs/f2fs/file.c:1657 [inline]
> f2fs_zero_range+0x10c1/0x1580 fs/f2fs/file.c:1737
> f2fs_fallocate+0x583/0x990 fs/f2fs/file.c:2030
> vfs_fallocate+0x669/0x7e0 fs/open.c:342
> ioctl_preallocate fs/ioctl.c:289 [inline]
> file_ioctl+0x611/0x780 fs/ioctl.c:-1
> do_vfs_ioctl+0xb33/0x1430 fs/ioctl.c:576
> __do_sys_ioctl fs/ioctl.c:595 [inline]
> __se_sys_ioctl+0x82/0x170 fs/ioctl.c:583
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f07bc58eec9
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to avoid updating zero-sized extent in extent cache
https://git.kernel.org/jaegeuk/f2fs/c/cbd96c6e304f
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-11-11 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:42 [PATCH v2] f2fs: fix to avoid updating zero-sized extent in extent cache Chao Yu
2025-11-11 22:50 ` 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=176290141749.3596344.15754105220634232444.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@kernel.org \
--cc=syzbot+24124df3170c3638b35f@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