From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate node blocks for atomic write block replacement
Date: Mon, 24 Apr 2023 23:47:20 +0800 [thread overview]
Message-ID: <32d4cb93-1491-4d1b-7713-61369a93f658@kernel.org> (raw)
In-Reply-To: <20230424154440.23279-1-daeho43@gmail.com>
On 2023/4/24 23:44, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> When a node block is missing for atomic write block replacement, we need
> to allocate it in advance of the replacement.
>
> Fixes: 3db1de0e582c ("f2fs: change the current atomic write way")
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2023-04-24 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:44 [PATCH] f2fs: allocate node blocks for atomic write block replacement Daeho Jeong
2023-04-24 15:47 ` Chao Yu [this message]
2023-04-24 18:10 ` [f2fs-dev] " patchwork-bot+f2fs
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 17:42 Daeho Jeong
2023-04-21 2:25 ` [f2fs-dev] " Chao Yu
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=32d4cb93-1491-4d1b-7713-61369a93f658@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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