From: Josef Bacik <jbacik@fusionio.com>
To: Liu Bo <liubo2009@cn.fujitsu.com>
Cc: Alexander Block <ablock84@googlemail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] Btrfs: update subvol_getflags/setflags to know new args from user
Date: Tue, 3 Jul 2012 12:08:14 -0400 [thread overview]
Message-ID: <20120703160814.GF6185@localhost.localdomain> (raw)
In-Reply-To: <4FF2DFD6.2020504@cn.fujitsu.com>
On Tue, Jul 03, 2012 at 06:04:38AM -0600, Liu Bo wrote:
> On 07/03/2012 07:27 PM, Alexander Block wrote:
>
> > On Fri, Jun 29, 2012 at 11:59 AM, Liu Bo <liubo2009@cn.fujitsu.com> wrote:
> >> I've modified 'btrfs subvolume list' to show a subvolume's attributes,
> >> such as readonly and default, and adopted a new structure for args for
> >> subvol_getflags/setflags.
> >>
> >> So here is the kernel side update.
> >>
> >> Signed-off-by: Liu Bo <liubo2009@cn.fujitsu.com>
> >> ---
> >> fs/btrfs/ioctl.c | 100 ++++++++++++++++++++++++++++++++++++++++-------------
> >> fs/btrfs/ioctl.h | 5 +++
> >> 2 files changed, 80 insertions(+), 25 deletions(-)
> >>
>
>
> [...]
>
>
> >> diff --git a/fs/btrfs/ioctl.h b/fs/btrfs/ioctl.h
> >> index 3186d2d..1fa0ce2 100644
> >> --- a/fs/btrfs/ioctl.h
> >> +++ b/fs/btrfs/ioctl.h
> >> @@ -45,6 +45,11 @@ struct btrfs_ioctl_vol_args_v2 {
> >> char name[BTRFS_SUBVOL_NAME_MAX + 1];
> >> };
> >>
> >> +struct btrfs_ioctl_get_set_flags_args {
> >> + __u64 objectid;
> >> + __u64 flags;
> >> +};
> >> +
> > Shouldn't BTRFS_IOC_SUBVOL_GETFLAGS/BTRFS_IOC_SUBVOL_SETFLAGS also be
> > updated? Both still have __u64 as arguments. Also, my patches for the
> > new btrfs prop command group won't work anymore due to the change in
> > the ioctl. I'm in the middle of preparing btrfs send/receive to be
> > sent to the list...I also use the ioctls there and we should agree on
> > what to do with the ioctls before I send the patches out.
>
>
> Just drop this patch, I've discussed with Ilya about it (and also CCed you).
>
> If we've more properties pending to set/get, 'btrfs property' will be better.
>
> So please go on your work, I'll try to rebase my patch on yours.
>
I've dropped the entire series from btrfs-next because without this patch the
other one fails to build without __btrfs_subvol_get_root. Resend if you want
the other patches included. Thanks,
Josef
next prev parent reply other threads:[~2012-07-03 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 9:59 [PATCH 1/3] Btrfs: add default support for subvol getflags Liu Bo
2012-06-29 9:59 ` [PATCH 2/3] Btrfs: update subvol_getflags/setflags to know new args from user Liu Bo
2012-07-03 11:27 ` Alexander Block
2012-07-03 12:04 ` Liu Bo
2012-07-03 12:09 ` Alexander Block
2012-07-03 16:08 ` Josef Bacik [this message]
2012-07-04 0:57 ` Liu Bo
2012-06-29 9:59 ` [PATCH 3/3] Btrfs: use helper function to simplify code Liu Bo
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=20120703160814.GF6185@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=ablock84@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.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).