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: Fri, 21 Apr 2023 10:25:45 +0800 [thread overview]
Message-ID: <7735439b-7f9d-3344-8c7a-6d5ad2a6712b@kernel.org> (raw)
In-Reply-To: <20230418174201.3274634-1-daeho43@gmail.com>
On 2023/4/19 1:42, 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.
Miss a fixes line?
Otherwise it looks good to me.
Thanks,
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> fs/f2fs/segment.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index c35476b3c075..0e1e29800934 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -217,7 +217,7 @@ static int __replace_atomic_write_block(struct inode *inode, pgoff_t index,
>
> retry:
> set_new_dnode(&dn, inode, NULL, NULL, 0);
> - err = f2fs_get_dnode_of_data(&dn, index, LOOKUP_NODE_RA);
> + err = f2fs_get_dnode_of_data(&dn, index, ALLOC_NODE);
> if (err) {
> if (err == -ENOMEM) {
> f2fs_io_schedule_timeout(DEFAULT_IO_TIMEOUT);
next prev parent reply other threads:[~2023-04-21 2:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 17:42 Daeho Jeong
2023-04-21 2:25 ` Chao Yu [this message]
2023-04-24 15:44 Daeho Jeong
2023-04-24 15:47 ` [f2fs-dev] " Chao Yu
2023-04-24 18:10 ` patchwork-bot+f2fs
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=7735439b-7f9d-3344-8c7a-6d5ad2a6712b@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
all inboxes | Powered by JetHome®