From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Wenjie Qi <qwjhust@gmail.com>
Cc: daehojeong@google.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, qiwenjie@xiaomi.com,
jaegeuk@kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: keep atomic write retry from zeroing original data
Date: Mon, 15 Jun 2026 15:30:09 +0000 [thread overview]
Message-ID: <178153740988.3946007.10376202781077694557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260527120628.2255597-1-qiwenjie@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 27 May 2026 20:06:28 +0800 you wrote:
> A partial atomic write reserves a block in the COW inode before reading the
> original data page for the untouched bytes in that page.
>
> If that read fails, write_begin returns an error but leaves the COW inode
> entry as NEW_ADDR. A retry of the same partial write then finds the COW
> entry, treats it as existing COW data, and f2fs_write_begin() zeroes the
> whole folio because blkaddr is NEW_ADDR.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: keep atomic write retry from zeroing original data
https://git.kernel.org/jaegeuk/f2fs/c/b5d5ab1ebe69
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-06-15 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 12:06 [f2fs-dev] [PATCH] f2fs: keep atomic write retry from zeroing original data Wenjie Qi
2026-06-11 8:12 ` Chao Yu via Linux-f2fs-devel
2026-06-15 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=178153740988.3946007.10376202781077694557.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=daehojeong@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=qiwenjie@xiaomi.com \
--cc=qwjhust@gmail.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