From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, zhiguo.niu@unisoc.com,
linux-f2fs-devel@lists.sourceforge.net, stable@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: compress: fix to handle race between truncate and writeback
Date: Mon, 14 Sep 2026 15:30:10 +0000 [thread overview]
Message-ID: <178939981087.647967.11998154111003241428.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260910141126.1309794-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 10 Sep 2026 22:11:26 +0800 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> fsstress reports a kernel BUG in f2fs_truncate_partial_cluster():
>
> kernel BUG at fs/f2fs/compress.c:1238!
> RIP: 0010:f2fs_truncate_partial_cluster+0x292/0x2a0
> Call Trace:
> <TASK>
> f2fs_truncate+0xf6/0x210
> f2fs_setattr+0x6b7/0x770
> notify_change+0x33b/0x520
> do_truncate+0xc2/0xf0
> vfs_truncate+0x153/0x1d0
> ksys_truncate+0x78/0xd0
> __x64_sys_truncate+0x16/0x20
> do_syscall_64+0xbe/0x540
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: compress: fix to handle race between truncate and writeback
https://git.kernel.org/jaegeuk/f2fs/c/c0337e331b06
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-09-14 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 14:11 [f2fs-dev] [PATCH v2] f2fs: compress: fix to handle race between truncate and writeback Chao Yu via Linux-f2fs-devel
2026-09-14 15:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=178939981087.647967.11998154111003241428.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=stable@kernel.org \
--cc=zhiguo.niu@unisoc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.