From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 2/4] Btrfs: use cross mount point check for cloning and deduplication
Date: Wed, 12 Dec 2018 18:05:57 +0000 [thread overview]
Message-ID: <20181212180559.15249-3-fdmanana@kernel.org> (raw)
In-Reply-To: <20181212180559.15249-1-fdmanana@kernel.org>
From: Filipe Manana <fdmanana@suse.com>
There is no reason why this check was performed for clone operations but
not for deduplication operations, after all deduplication is a special
case of cloning. So make the check happen for deduplication as well.
This check used to be done and got removed by accident in commit
2b3909f8a7fe9 ("btrfs: use new dedupe data function pointer").
Fixes: 2b3909f8a7fe9 ("btrfs: use new dedupe data function pointer").
Signed-off-by: Filipe Manana <fdmanana@suse.com>
---
fs/btrfs/ioctl.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 1e90d10b5638..ffe940ceb80a 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -3912,12 +3912,12 @@ 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;
}
+ if (file_in->f_path.mnt != file_out->f_path.mnt ||
+ inode_in->i_sb != inode_out->i_sb)
+ return -EXDEV;
+
if (same_inode)
inode_lock(inode_in);
else
--
2.11.0
next prev parent reply other threads:[~2018-12-12 18:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 18:05 [PATCH 0/4] Btrfs: a few more cleanups and fixes for clone/deduplication fdmanana
2018-12-12 18:05 ` [PATCH 1/4] Btrfs: move duplicated nodatasum check into common reflink/dedupe helper fdmanana
2019-01-11 14:55 ` David Sterba
2018-12-12 18:05 ` fdmanana [this message]
2018-12-13 16:02 ` [PATCH 2/4] Btrfs: use cross mount point check for cloning and deduplication David Sterba
2019-01-11 14:38 ` David Sterba
2018-12-12 18:05 ` [PATCH 3/4] Btrfs: check if destination root is read-only for deduplication fdmanana
2018-12-13 16:07 ` David Sterba
2019-01-31 16:39 ` Filipe Manana
2019-01-31 16:44 ` Hugo Mills
2019-02-18 15:38 ` David Sterba
2019-02-18 16:55 ` Filipe Manana
2019-02-12 17:59 ` Filipe Manana
2019-02-20 16:41 ` Zygo Blaxell
2019-02-20 16:54 ` Filipe Manana
2019-02-20 17:17 ` Zygo Blaxell
2019-02-22 11:13 ` Filipe Manana
2019-02-22 17:25 ` David Sterba
2019-02-21 16:54 ` Zygo Blaxell
2019-02-18 16:01 ` David Sterba
2018-12-12 18:05 ` [PATCH 4/4] Btrfs: remove no longer needed range length checks " fdmanana
2018-12-13 12:20 ` Nikolay Borisov
2019-01-31 16:31 ` Filipe Manana
2019-02-12 17:58 ` Filipe Manana
2019-02-18 15:10 ` David Sterba
2018-12-13 12:19 ` [PATCH 0/4] Btrfs: a few more cleanups and fixes for clone/deduplication Nikolay Borisov
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=20181212180559.15249-3-fdmanana@kernel.org \
--to=fdmanana@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).