All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhangqilong via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>, "jaegeuk@kernel.org" <jaegeuk@kernel.org>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] 答复: 答复:  答复: [PATCH] f2fs: Fix data consistency in f2fs_move_file_range()
Date: Tue, 25 Oct 2022 07:01:35 +0000	[thread overview]
Message-ID: <411daf4a5ff94907bc298579f1e99d49@huawei.com> (raw)
In-Reply-To: <959ca5cb-947c-d693-5e6f-79736ada7664@kernel.org>

> On 2022/10/25 14:27, zhangqilong wrote:
> >> On 2022/10/20 15:27, zhangqilong via Linux-f2fs-devel wrote:
> >>>> On 2022/10/18 10:45, Zhang Qilong wrote:
> >>>>> In the following case:
> >>>>> process 1			process 2
> >>>>>     ->open A
> >>>>>      ->mmap
> >>>>>       ->read # the first time
> >>>>>       				 ->ioctl w/h F2FS_IOC_MOVE_RANGE
> >>>>> 				        	# (range A->B)
> >>>>>       ->read # the second time
> >>>>
> >>>> How about checking B as well? Previous mapped data can still be
> >>>> accessed after F2FS_IOC_MOVE_RANGE?
> >>>>
> >>>
> >>> Hi
> >>>
> >>> I have checked B as well. Previous mapped data can't be accessed
> >>> after F2FS_IOC_MOVE_RANGE.
> >>
> >> I doubt that we didn't call flush_dcache_page() in below branch, so
> >> user may see stall data after F2FS_IOC_MOVE_RANGE? Am I missing
> something?
> >>
> >
> > Hi,
> >
> > You are right, it needs flush_dcache_page, but it is unnecessary here,
> > the __clone_blkaddrs() is called by FALLOC_FL_COLLAPSE_RANGE/
> FALLOC_FL_INSERT_RANGE /F2FS_IOC_MOVE_RANGE.
> > ->__exchange_data_block()
> >   ->__clone_blkaddrs()
> >
> > f2fs_do_collapse()  and f2fs_insert_range() have truncate_pagecache
> > after __exchange_data_block() It seem we have analyzed before. So we
> only need to add a truncate operation for F2FS_IOC_MOVE_RANGE.
> 
> I mean it needs to call truncate_pagecache_range(dst, ...) in
> f2fs_move_file_range() as well, right?

Yes, I think it should call truncate_pagecache_range(dst, ...) or flush_dcache_page() here.
I submitted a patch before, it seems to be forgetten.

https://lore.kernel.org/linux-f2fs-devel/20220825024102.120651-1-zhangqilong3@huawei.com/

But, I test it w/o truncate_pagecache_range(dst, ...) or flush_dcache_page(), user can not
see stall dst data, maybe It is a bit difficult to construct the scene for me.

Thanks,
> 
> Thanks,
> 
> >
> >> __clone_blkaddrs()
> >> {
> >> ...
> >> 		} else {
> >> 			struct page *psrc, *pdst;
> >>
> >> 			psrc = f2fs_get_lock_data_page(src_inode,
> >> 							src + i, true);
> >> 			if (IS_ERR(psrc))
> >> 				return PTR_ERR(psrc);
> >> 			pdst = f2fs_get_new_data_page(dst_inode, NULL,
> dst + i,
> >> 								true);
> >> 			if (IS_ERR(pdst)) {
> >> 				f2fs_put_page(psrc, 1);
> >> 				return PTR_ERR(pdst);
> >> 			}
> >> 			memcpy_page(pdst, 0, psrc, 0, PAGE_SIZE);
> >> 			set_page_dirty(pdst);
> >> 			f2fs_put_page(pdst, 1);
> >> 			f2fs_put_page(psrc, 1);
> >>
> >> 			ret = f2fs_truncate_hole(src_inode,
> >> 						src + i, src + i + 1);
> >> 			if (ret)
> >> 				return ret;
> >> 			i++;
> >> 		}
> >> ...
> >> }
> >>
> >> Thanks,
> >>
> >>>
> >>> In addition, this patch could be applied to mainline if possible?
> >>>
> >>> Thanks
> >>>
> >>>> Thanks,
> >>>>
> >>>>>
> >>>>> We will read old data at the second time. The root cause is that
> >>>>> user still can see the previous source data after being moved. We
> >>>>> fix it by adding truncating after __exchange_data_block.
> >>>>>
> >>>>> Fixes: 4dd6f977fc77 ("f2fs: support an ioctl to move a range of
> >>>>> data
> >>>>> blocks")
> >>>>> Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
> >>>>> ---
> >>>>> v2:
> >>>>> - moving truncating to the range of f2fs_lock_op()
> >>>>>
> >>>>> v3:
> >>>>> - modify the title and commit message
> >>>>> ---
> >>>>>     fs/f2fs/file.c | 3 +++
> >>>>>     1 file changed, 3 insertions(+)
> >>>>>
> >>>>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index
> >>>>> 82cda1258227..e9dfa41baf9e 100644
> >>>>> --- a/fs/f2fs/file.c
> >>>>> +++ b/fs/f2fs/file.c
> >>>>> @@ -2824,6 +2824,7 @@ static int f2fs_move_file_range(struct file
> >>>>> *file_in,
> >>>> loff_t pos_in,
> >>>>>     			goto out_src;
> >>>>>     	}
> >>>>>
> >>>>> +	filemap_invalidate_lock(src->i_mapping);
> >>>>>     	f2fs_lock_op(sbi);
> >>>>>     	ret = __exchange_data_block(src, dst, pos_in >>
> F2FS_BLKSIZE_BITS,
> >>>>>     				pos_out >> F2FS_BLKSIZE_BITS, @@
> -2835,7
> >> +2836,9 @@ static
> >>>>> int f2fs_move_file_range(struct file *file_in,
> >>>> loff_t pos_in,
> >>>>>     		else if (dst_osize != dst->i_size)
> >>>>>     			f2fs_i_size_write(dst, dst_osize);
> >>>>>     	}
> >>>>> +	truncate_pagecache_range(src, pos_in, pos_in + len - 1);
> >>>>>     	f2fs_unlock_op(sbi);
> >>>>> +	filemap_invalidate_unlock(src->i_mapping);
> >>>>>
> >>>>>     	if (src != dst)
> >>>>>     		f2fs_up_write(&F2FS_I(dst)->i_gc_rwsem[WRITE]);
> >>>
> >>> _______________________________________________
> >>> Linux-f2fs-devel mailing list
> >>> Linux-f2fs-devel@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2022-10-25  7:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  2:45 [f2fs-dev] [PATCH] f2fs: Fix data consistency in f2fs_move_file_range() Zhang Qilong via Linux-f2fs-devel
2022-10-18  2:45 ` [f2fs-dev] [PATCH] f2fs: Fix the race condition of resize flag between resizefs Zhang Qilong via Linux-f2fs-devel
2022-10-20  1:19   ` Chao Yu
2022-10-20  1:29 ` [f2fs-dev] [PATCH] f2fs: Fix data consistency in f2fs_move_file_range() Chao Yu
2022-10-20  7:27   ` [f2fs-dev] 答复: " zhangqilong via Linux-f2fs-devel
2022-10-25  1:17     ` Chao Yu
2022-10-25  6:27       ` [f2fs-dev] 答复: " zhangqilong via Linux-f2fs-devel
2022-10-25  6:41         ` Chao Yu
2022-10-25  7:01           ` zhangqilong via Linux-f2fs-devel [this message]
2022-10-25  7:20             ` [f2fs-dev] 答复: " Chao Yu
2022-10-25  7:36               ` [f2fs-dev] 答复: " zhangqilong via Linux-f2fs-devel
2022-10-25  7:54                 ` 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=411daf4a5ff94907bc298579f1e99d49@huawei.com \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=zhangqilong3@huawei.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.