From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: dsterba@suse.cz, Mark Fasheh <mfasheh@suse.de>,
Chris Mason <clm@fb.com>, Josef Bacik <jbacik@fb.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/5] btrfs: add no_mtime flag to btrfs-extent-same
Date: Wed, 24 Jun 2015 16:17:32 -0400 [thread overview]
Message-ID: <20150624201732.GA14931@hungrycats.org> (raw)
In-Reply-To: <20150623151156.GI6761@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 6006 bytes --]
On Tue, Jun 23, 2015 at 05:11:56PM +0200, David Sterba wrote:
> On Mon, Jun 22, 2015 at 03:47:42PM -0700, Mark Fasheh wrote:
> > --- a/fs/btrfs/ioctl.c
> > +++ b/fs/btrfs/ioctl.c
> > @@ -87,7 +87,8 @@ struct btrfs_ioctl_received_subvol_args_32 {
> >
> >
> > static int btrfs_clone(struct inode *src, struct inode *inode,
> > - u64 off, u64 olen, u64 olen_aligned, u64 destoff);
> > + u64 off, u64 olen, u64 olen_aligned, u64 destoff,
> > + int no_mtime);
>
> Please make it 'flags' and pass the verified flags directly.
>
> > /* Mask out flags that are inappropriate for the given type of inode. */
> > static inline __u32 btrfs_mask_flags(umode_t mode, __u32 flags)
> > @@ -2974,7 +2975,7 @@ static int extent_same_check_offsets(struct inode *inode, u64 off, u64 *plen,
> > }
> >
> > static int btrfs_extent_same(struct inode *src, u64 loff, u64 olen,
> > - struct inode *dst, u64 dst_loff)
> > + struct inode *dst, u64 dst_loff, int no_mtime)
> > {
> > int ret;
> > u64 len = olen;
> > @@ -3054,7 +3055,8 @@ static int btrfs_extent_same(struct inode *src, u64 loff, u64 olen,
> > /* pass original length for comparison so we stay within i_size */
> > ret = btrfs_cmp_data(src, loff, dst, dst_loff, olen, &cmp);
> > if (ret == 0)
> > - ret = btrfs_clone(src, dst, loff, olen, len, dst_loff);
> > + ret = btrfs_clone(src, dst, loff, olen, len, dst_loff,
> > + no_mtime);
> >
> > if (same_inode)
> > unlock_extent(&BTRFS_I(src)->io_tree, same_lock_start,
> > @@ -3088,6 +3090,7 @@ static long btrfs_ioctl_file_extent_same(struct file *file,
> > u64 bs = BTRFS_I(src)->root->fs_info->sb->s_blocksize;
> > bool is_admin = capable(CAP_SYS_ADMIN);
> > u16 count;
> > + int no_mtime = 0;
> >
> > if (!(file->f_mode & FMODE_READ))
> > return -EINVAL;
> > @@ -3139,6 +3142,12 @@ static long btrfs_ioctl_file_extent_same(struct file *file,
> > if (!S_ISREG(src->i_mode))
> > goto out;
> >
> > + ret = -EINVAL;
> > + if (same->flags & ~BTRFS_SAME_FLAGS)
> > + goto out;
> > + if (same->flags & BTRFS_SAME_NO_MTIME)
> > + no_mtime = 1;
> > +
> > /* pre-format output fields to sane values */
> > for (i = 0; i < count; i++) {
> > same->info[i].bytes_deduped = 0ULL;
> > @@ -3164,7 +3173,8 @@ static long btrfs_ioctl_file_extent_same(struct file *file,
> > info->status = -EACCES;
> > } else {
> > info->status = btrfs_extent_same(src, off, len, dst,
> > - info->logical_offset);
> > + info->logical_offset,
> > + no_mtime);
> > if (info->status == 0)
> > info->bytes_deduped += len;
> > }
> > @@ -3219,13 +3229,17 @@ static int clone_finish_inode_update(struct btrfs_trans_handle *trans,
> > struct inode *inode,
> > u64 endoff,
> > const u64 destoff,
> > - const u64 olen)
> > + const u64 olen,
> > + int no_mtime)
> > {
> > struct btrfs_root *root = BTRFS_I(inode)->root;
> > int ret;
> >
> > inode_inc_iversion(inode);
> > - inode->i_mtime = inode->i_ctime = CURRENT_TIME;
> > + if (no_mtime)
> > + inode->i_ctime = CURRENT_TIME;
> > + else
> > + inode->i_mtime = inode->i_ctime = CURRENT_TIME;
> > /*
> > * We round up to the block size at eof when determining which
> > * extents to clone above, but shouldn't round up the file size.
> > @@ -3316,7 +3330,7 @@ static void clone_update_extent_map(struct inode *inode,
> > */
> > static int btrfs_clone(struct inode *src, struct inode *inode,
> > const u64 off, const u64 olen, const u64 olen_aligned,
> > - const u64 destoff)
> > + const u64 destoff, int no_mtime)
> > {
> > struct btrfs_root *root = BTRFS_I(inode)->root;
> > struct btrfs_path *path = NULL;
> > @@ -3640,7 +3654,7 @@ process_slot:
> > root->sectorsize);
> > ret = clone_finish_inode_update(trans, inode,
> > last_dest_end,
> > - destoff, olen);
> > + destoff, olen, no_mtime);
> > if (ret)
> > goto out;
> > if (new_key.offset + datal >= destoff + len)
> > @@ -3678,7 +3692,7 @@ process_slot:
> > clone_update_extent_map(inode, trans, NULL, last_dest_end,
> > destoff + len - last_dest_end);
> > ret = clone_finish_inode_update(trans, inode, destoff + len,
> > - destoff, olen);
> > + destoff, olen, no_mtime);
> > }
> >
> > out:
> > @@ -3808,7 +3822,7 @@ static noinline long btrfs_ioctl_clone(struct file *file, unsigned long srcfd,
> > btrfs_double_extent_lock(src, off, inode, destoff, len);
> > }
> >
> > - ret = btrfs_clone(src, inode, off, olen, len, destoff);
> > + ret = btrfs_clone(src, inode, off, olen, len, destoff, 0);
> >
> > if (same_inode) {
> > u64 lock_start = min_t(u64, off, destoff);
> > diff --git a/include/uapi/linux/btrfs.h b/include/uapi/linux/btrfs.h
> > index b6dec05..beeb51c 100644
> > --- a/include/uapi/linux/btrfs.h
> > +++ b/include/uapi/linux/btrfs.h
>
> > +#define BTRFS_SAME_NO_MTIME 0x1
> > +#define BTRFS_SAME_FLAGS (BTRFS_SAME_NO_MTIME)
>
> The naming scheme used eg. for the send flags:
>
> BTRFS_SEND_FLAG_MASK
> BTRFS_SEND_FLAG_NO_FILE_DATA
>
> So I suggest to follow it:
>
> BTRFS_SAME_FLAG_MASK
> BTRFS_SAME_FLAG_NO_MTIME
>
> Though I'd rather see it named it with BTRFS_EXTENT_SAME_ prefix so it
> (almost ...) matches the ioctl name (and is greppable).
Is there any sane use case where we would _want_ EXTENT_SAME to change
the mtime? We do a lot of work to make sure that none of the files
involved have any sort of content change. Why do we need the flag at all?
> This is going to be in a public interface so the naming is important.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2015-06-24 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 22:47 [PATCH 0/5] btrfs: dedupe fixes, features V2 Mark Fasheh
2015-06-22 22:47 ` [PATCH 1/5] btrfs: pass unaligned length to btrfs_cmp_data() Mark Fasheh
2015-06-22 22:47 ` [PATCH 2/5] btrfs: fix deadlock with extent-same and readpage Mark Fasheh
2015-06-22 22:47 ` [PATCH 3/5] btrfs: fix clone / extent-same deadlocks Mark Fasheh
2015-06-23 14:56 ` David Sterba
2015-06-22 22:47 ` [PATCH 4/5] btrfs: allow dedupe of same inode Mark Fasheh
2015-06-23 14:59 ` David Sterba
2015-06-22 22:47 ` [PATCH 5/5] btrfs: add no_mtime flag to btrfs-extent-same Mark Fasheh
2015-06-23 15:11 ` David Sterba
2015-06-23 17:11 ` Mark Fasheh
2015-06-24 20:17 ` Zygo Blaxell [this message]
2015-06-25 12:52 ` David Sterba
2015-06-25 13:10 ` Austin S Hemmelgarn
2015-06-25 16:52 ` Zygo Blaxell
2015-06-25 18:12 ` Mark Fasheh
-- strict thread matches above, loose matches on Subject: below --
2015-06-23 21:28 [PATCH 0/5] btrfs: dedupe fixes, features V3 Mark Fasheh
2015-06-23 21:28 ` [PATCH 5/5] btrfs: add no_mtime flag to btrfs-extent-same Mark Fasheh
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=20150624201732.GA14931@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@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