From: Nikolay Borisov <nborisov@suse.com>
To: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] btrfs: remove the cross file system checks from remap
Date: Fri, 18 Feb 2022 15:22:52 +0200 [thread overview]
Message-ID: <532a5d22-0601-8a98-e4d4-fb1d433394e9@suse.com> (raw)
In-Reply-To: <1ebfca5a-4aeb-ce63-f9c7-5a4444a2773d@suse.com>
On 18.02.22 г. 15:15 ч., Nikolay Borisov wrote:
>
>
> On 16.02.22 г. 22:06 ч., Josef Bacik wrote:
>> This is handled in the generic VFS helper, we do not need to duplicate
>> this inside of btrfs.
>>
>> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
>> ---
>> fs/btrfs/reflink.c | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>> diff --git a/fs/btrfs/reflink.c b/fs/btrfs/reflink.c
>> index a3930da4eb3f..4425030e09cb 100644
>> --- a/fs/btrfs/reflink.c
>> +++ b/fs/btrfs/reflink.c
>> @@ -771,10 +771,6 @@ static int btrfs_remap_file_range_prep(struct
>> file *file_in, loff_t pos_in,
>> if (btrfs_root_readonly(root_out))
>> return -EROFS;
>> -
>> - if (file_in->f_path.mnt != file_out->f_path.mnt ||
>> - inode_in->i_sb != inode_out->i_sb)
>> - return -EXDEV;
>
> Where exactly is this check performed in the vfs because I can't see
> anything in generic_remap_file_range_prep.
Ah it depends on another patch in the ML which is not part of the same
series. Fair enough, though I agree with David's suggestion to have an
assert just in case.
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
>
>> }
>> /* Don't make the dst file partly checksummed */
prev parent reply other threads:[~2022-02-18 13:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 20:06 [PATCH] btrfs: remove the cross file system checks from remap Josef Bacik
2022-02-16 21:37 ` David Sterba
2022-02-18 13:15 ` Nikolay Borisov
2022-02-18 13:22 ` Nikolay Borisov [this message]
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=532a5d22-0601-8a98-e4d4-fb1d433394e9@suse.com \
--to=nborisov@suse.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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