From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jiucheng Xu <jiucheng.xu@amlogic.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PING][PATCH] f2fs: force out‑place update for all writes on compressed file
Date: Mon, 7 Sep 2026 15:08:07 +0800 [thread overview]
Message-ID: <b90c9052-b44b-404a-85cc-8221249b63d7@kernel.org> (raw)
In-Reply-To: <5de3d9c8-e847-422f-a9e4-31ac2a1b5c2e@amlogic.com>
On 9/2/26 11:18, Jiucheng Xu wrote:
> Hi f2fs maintainers,
Jiucheng,
Sorry for delay reply.
>
> Gentle ping for this patch:
> Link: https://lore.kernel.org/r/20260826-origin-dev-v1-1-c21271a82100@amlogic.com
>
> For compressed file, compressed write may fail and fall back to raw
> write.
> If in-place update(IPU) is allowed, raw data could be written into disk
> before cluster metadata is updated from compressed state to raw state.
> Sudden power-cut during this window will result in inconsistency:
> raw data on disk but metadata still expects compressed content,
> which causes decompression failure when reading the file later.
I didn't get it, can you please describe the issue w/ call stack in race condition?
>
> To eliminate this risk completely, force out-place update for all
> write operations on compressed file, so IPU will never be used.
>
> Could you please take a look at your convenience?
> Any comments are welcome.
>
> Thanks,
> Jiucheng
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next parent reply other threads:[~2026-09-07 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5de3d9c8-e847-422f-a9e4-31ac2a1b5c2e@amlogic.com>
2026-09-07 7:08 ` Chao Yu via Linux-f2fs-devel [this message]
2026-09-07 8:45 ` [f2fs-dev] [PING][PATCH] f2fs: force out‑place update for all writes on compressed file Jiucheng Xu via Linux-f2fs-devel
2026-09-07 10:38 ` Chao Yu via Linux-f2fs-devel
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=b90c9052-b44b-404a-85cc-8221249b63d7@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jiucheng.xu@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 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.