linux-f2fs-devel.lists.sourceforge.net archive mirror
 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: Thu, 20 Oct 2022 07:27:52 +0000	[thread overview]
Message-ID: <1e8cf37922cc4c87aff770449bbba4ab@huawei.com> (raw)
In-Reply-To: <35811a40-cc69-a50d-b348-62eed5ed1227@kernel.org>

> 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.

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

  reply	other threads:[~2022-10-20  7:29 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   ` zhangqilong via Linux-f2fs-devel [this message]
2022-10-25  1:17     ` [f2fs-dev] 答复: " 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           ` [f2fs-dev] 答复: " zhangqilong via Linux-f2fs-devel
2022-10-25  7:20             ` 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=1e8cf37922cc4c87aff770449bbba4ab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).