[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7735439b-7f9d-3344-8c7a-6d5ad2a6712b@kernel.org>
Date: Fri, 21 Apr 2023 10:25:45 +0800
From: Chao Yu <chao@...nel.org>
To: Daeho Jeong <daeho43@...il.com>, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, kernel-team@...roid.com
Cc: Daeho Jeong <daehojeong@...gle.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate node blocks for atomic write
block replacement
On 2023/4/19 1:42, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@...gle.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@...gle.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);
Powered by blists - more mailing lists