From: patchwork-bot+f2fs@kernel.org
To: Jiucheng Xu <jiucheng.xu@amlogic.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
devnull+jiucheng.xu.amlogic.com@kernel.org,
jianxin.pan@amlogic.com, tuan.zhang@amlogic.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, tao.zeng@amlogic.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: force out-place update for all writes on compressed file
Date: Mon, 14 Sep 2026 15:30:07 +0000 [thread overview]
Message-ID: <178939980787.647967.18277345902202465744.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260907-origin-dev-v1-1-85ae7ebc8c98@amlogic.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 07 Sep 2026 19:35:42 +0800 you wrote:
> From: Jiucheng Xu <jiucheng.xu@amlogic.com>
>
> For compressed file, compressed write may fail and fall back to raw
> write.
>
> -Thread A - Thread B
> - f2fs_write_multi_pages - f2fs_down_write(&sbi->cp_rwsem);
> - f2fs_write_compressed_pages - ...
> - f2fs_trylock_op - ...
> - f2fs_down_read_trylock(&sbi->cp_rwsem); - ...
> - f2fs_write_raw_pages - ...
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: force out-place update for all writes on compressed file
https://git.kernel.org/jaegeuk/f2fs/c/a64a3fec11e7
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:[~2026-09-14 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 11:35 Jiucheng Xu via B4 Relay
2026-09-08 0:15 ` Chao Yu
2026-09-14 15:30 ` 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=178939980787.647967.18277345902202465744.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=devnull+jiucheng.xu.amlogic.com@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jianxin.pan@amlogic.com \
--cc=jiucheng.xu@amlogic.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tao.zeng@amlogic.com \
--cc=tuan.zhang@amlogic.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®