From: Filipe Manana <fdmanana@gmail.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 3/3] btrfs: Perform locking/unlocking in btrfs_remap_file_range()
Date: Tue, 26 Feb 2019 12:08:09 +0000 [thread overview]
Message-ID: <CAL3q7H4JXORsxn5LB2ZK2Mg2wSyZcSgq3P4zFavN-nLQyn2V-A@mail.gmail.com> (raw)
In-Reply-To: <20190225190744.21664-3-rgoldwyn@suse.de>
On Mon, Feb 25, 2019 at 7:08 PM Goldwyn Rodrigues <rgoldwyn@suse.de> wrote:
>
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
>
> Moves code to make it more readable, so as locking and unlocking is
> done in the same function.
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
> ---
> fs/btrfs/ioctl.c | 53 +++++++++++++++++++++--------------------------------
> 1 file changed, 21 insertions(+), 32 deletions(-)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index 9c8e1734429c..f0ae1af91ff3 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -3975,22 +3975,6 @@ static int btrfs_remap_file_range_prep(struct file *file_in, loff_t pos_in,
> u64 wb_len;
> int ret;
>
> - if (!(remap_flags & REMAP_FILE_DEDUP)) {
> - struct btrfs_root *root_out = BTRFS_I(inode_out)->root;
> -
> - if (btrfs_root_readonly(root_out))xfs_reflink_remap_prep
> - return -EROFS;
> -
> - if (file_in->f_path.mnt != file_out->f_path.mnt ||
> - inode_in->i_sb != inode_out->i_sb)
> - return -EXDEV;
> - }
Why move these checks?
The goal of the _prep function (both btrfs and vfs) is to have the
checks for all needed conditions in one place.
As for the lock/unlock, it follows the same pattern from xfs
(xfs_reflink_remap_prep and xfs_file_remap_range).
No complaints about changing this, I'm just neutral about it.
> -
> - if (same_inode)
> - inode_lock(inode_in);
> - else
> - btrfs_double_inode_lock(inode_in, inode_out);
> -
> /*
> * Now that the inodes are locked, we need to start writeback ourselves
> * and can not rely on the writeback from the VFS's generic helper
> @@ -4022,26 +4006,14 @@ static int btrfs_remap_file_range_prep(struct file *file_in, loff_t pos_in,
> ret = btrfs_wait_ordered_range(inode_in, ALIGN_DOWN(pos_in, bs),
> wb_len);
> if (ret < 0)
> - goto out_unlock;
> + return ret;
> ret = btrfs_wait_ordered_range(inode_out, ALIGN_DOWN(pos_out, bs),
> wb_len);
> if (ret < 0)
> - goto out_unlock;
> + return ret;
>
> - ret = generic_remap_file_range_prep(file_in, pos_in, file_out, pos_out,
> + return generic_remap_file_range_prep(file_in, pos_in, file_out, pos_out,
> len, remap_flags);
> - if (ret < 0 || *len == 0)
> - goto out_unlock;
> -
> - return 0;
> -
> - out_unlock:
> - if (same_inode)
> - inode_unlock(inode_in);
> - else
> - btrfs_double_inode_unlock(inode_in, inode_out);
> -
> - return ret;
> }
>
> loff_t btrfs_remap_file_range(struct file *src_file, loff_t off,
> @@ -4056,16 +4028,33 @@ loff_t btrfs_remap_file_range(struct file *src_file, loff_t off,
> if (remap_flags & ~(REMAP_FILE_DEDUP | REMAP_FILE_ADVISORY))
> return -EINVAL;
>
> + if (!(remap_flags & REMAP_FILE_DEDUP)) {
> + struct btrfs_root *root_out = BTRFS_I(dst_inode)->root;
> +
> + if (btrfs_root_readonly(root_out))
> + return -EROFS;
> +
> + if (src_file->f_path.mnt != dst_file->f_path.mnt ||
> + src_inode->i_sb != dst_inode->i_sb)
> + return -EXDEV;
> + }
> +
> + if (same_inode)
> + inode_lock(src_inode);
> + else
> + btrfs_double_inode_lock(src_inode, dst_inode);
> +
> ret = btrfs_remap_file_range_prep(src_file, off, dst_file, destoff,
> &len, remap_flags);
> if (ret < 0 || len == 0)
> - return ret;
> + goto out_unlock;
>
> if (remap_flags & REMAP_FILE_DEDUP)
> ret = btrfs_extent_same(src_inode, off, len, dst_inode, destoff);
> else
> ret = btrfs_clone_files(dst_file, src_file, off, len, destoff);
>
> +out_unlock:
> if (same_inode)
> inode_unlock(src_inode);
> else
> --
> 2.16.4
>
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
next prev parent reply other threads:[~2019-02-26 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 19:07 [PATCH 1/3] btrfs: Initialize btrfs_io_ctl instead of memsetting it Goldwyn Rodrigues
2019-02-25 19:07 ` [PATCH 2/3] btrfs: Initialize inode->i_op once in btrfs_symlink Goldwyn Rodrigues
2019-02-27 15:39 ` David Sterba
2019-02-25 19:07 ` [PATCH 3/3] btrfs: Perform locking/unlocking in btrfs_remap_file_range() Goldwyn Rodrigues
2019-02-26 12:08 ` Filipe Manana [this message]
2019-02-26 12:57 ` Goldwyn Rodrigues
2019-02-27 14:52 ` David Sterba
2019-02-27 15:06 ` David Sterba
2019-03-25 19:22 ` David Sterba
2019-02-27 15:47 ` [PATCH 1/3] btrfs: Initialize btrfs_io_ctl instead of memsetting it David Sterba
2019-02-27 17:02 ` Goldwyn Rodrigues
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=CAL3q7H4JXORsxn5LB2ZK2Mg2wSyZcSgq3P4zFavN-nLQyn2V-A@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.de \
/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).