linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Goffredo Baroncelli <kreijack@libero.it>
Cc: Andreas Philipp <philipp.andreas@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	lizf <lizf@cn.fujitsu.com>
Subject: Re: [PATCH 1/5] Add support for read-only subvolumes.
Date: Mon, 25 Apr 2011 19:24:29 -0400	[thread overview]
Message-ID: <1303773807-sup-7001@think> (raw)
In-Reply-To: <4DB5E8F6.1020807@libero.it>

Excerpts from Goffredo Baroncelli's message of 2011-04-25 17:34:46 -0400:
> Hi Andreas,
> 
> On 04/25/2011 03:47 PM, Andreas Philipp wrote:
> > Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
> > an option for the creation of a readonly snapshot.
> > 
> > Signed-off-by: Andreas Philipp <philipp.andreas@gmail.com>
> > ---
> >  btrfs_cmds.c |   44 ++++++++++++++++++++++++++++++++++++--------
> >  1 files changed, 36 insertions(+), 8 deletions(-)
> > 
> > diff --git a/btrfs_cmds.c b/btrfs_cmds.c
> > index 8031c58..baec675 100644
> > --- a/btrfs_cmds.c
> > +++ b/btrfs_cmds.c
> > @@ -43,7 +43,7 @@
> >  
> >  #ifdef __CHECKER__
> 
> It is not related to your parch.. but does anyone know why we re-define
> some constants if __CHECKER__ is defined ?

This is old support for the sparse program, which finds a good number of
bugs.

> 
> >  #define BLKGETSIZE64 0
> > -#define BTRFS_IOC_SNAP_CREATE 0
> > +#define BTRFS_IOC_SNAP_CREATE_V2 0
> >  #define BTRFS_VOL_NAME_MAX 255
> >  struct btrfs_ioctl_vol_args { char name[BTRFS_VOL_NAME_MAX]; };
> >  static inline int ioctl(int fd, int define, void *arg) { return 0; }
> > @@ -310,13 +310,34 @@ int do_subvol_list(int argc, char **argv)
> >  int do_clone(int argc, char **argv)
> >  {
> >      char    *subvol, *dst;
> > -    int    res, fd, fddst, len;
> > +    int    res, fd, fddst, len, optind = 0, readonly = 0;
> >      char    *newname;
> >      char    *dstdir;
> >  
> > -    subvol = argv[1];
> > -    dst = argv[2];
> > -    struct btrfs_ioctl_vol_args    args;
> > +    while(1) {
> > +        int c = getopt(argc, argv, "r");
> > +        if (c < 0)
> > +            break;
> > +        switch(c) {
> > +            case 'r':
> > +                optind++;
> > +                readonly = 1;
> > +                break;
> > +                    default:
> > +                fprintf(stderr, "Invalid arguments for subvolume snapshot\n");
> > +                free(argv);
> > +                return 1;
> > +        }
> > +    }
> > +    if (argc - optind < 2) {
> > +        fprintf(stderr, "Invalid arguments for defragment\n");
>                                                        ^^^^^^^^^^^^
> 
> May be that you need to replace "defragment" with "subvolume snapshot" ?
> 
> > +        free(argv);
> > +        return 1;
> > +    }
> > +
> > +    subvol = argv[optind+1];
> > +    dst = argv[optind+2];
> > +    struct btrfs_ioctl_vol_args_v2    args;
> 
> Does the "standard C" allow to define a variable in the middle in a
> function instead of in the begin ?
> Anyway, even not required, I suggest to fill "args" by zero.

I'd prefer all the variables are at the stop of a scope.

> 
> +    memset(&args, 0, sizeog(args));
> 
> >  
> >      res = test_issubvolume(subvol);
> >      if(res<0){
> > @@ -371,12 +392,19 @@ int do_clone(int argc, char **argv)
> >          fprintf(stderr, "ERROR: can't access to '%s'\n", dstdir);
> >          return 12;
> >      }
> > +    
> > +    if (readonly) {
> > +        args.flags |= BTRFS_SUBVOL_RDONLY;
> > +        printf("Create a readonly snapshot of '%s' in '%s/%s'\n",
> > +               subvol, dstdir, newname);
> > +    }
> > +    else
> > +        printf("Create a snapshot of '%s' in '%s/%s'\n",
> > +               subvol, dstdir, newname);
> >  
> It is not required, but I suggest to use also in the "else" the brackets
> ( {} ).

Yes please.

> 
> > -    printf("Create a snapshot of '%s' in '%s/%s'\n",
> > -           subvol, dstdir, newname);
> >      args.fd = fd;
> >      strcpy(args.name, newname);
> > -    res = ioctl(fddst, BTRFS_IOC_SNAP_CREATE, &args);
> > +    res = ioctl(fddst, BTRFS_IOC_SNAP_CREATE_V2, &args);
> >  
> >      close(fd);
> >      close(fddst);
> 

-chris

  reply	other threads:[~2011-04-25 23:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25  1:24 Read Only snapshots David Morgado
2011-04-25 12:16 ` Chris Mason
2011-04-25 13:47   ` [PATCH 0/5] Add user-space support for read-only snapshot creation Andreas Philipp
2011-04-25 13:47     ` [PATCH 1/5] Add support for read-only subvolumes Andreas Philipp
2011-04-25 21:34       ` Goffredo Baroncelli
2011-04-25 23:24         ` Chris Mason [this message]
2011-04-26  6:06         ` Li Zefan
2011-04-26  5:48       ` Li Zefan
2011-04-26  5:50       ` Li Zefan
2011-04-25 13:47     ` [PATCH 2/5] Support the new parameters in do_clone(int argc, char** argv) Andreas Philipp
2011-04-25 13:47     ` [PATCH 3/5] Added support for an additional ioctl Andreas Philipp
2011-04-25 13:48     ` [PATCH 4/5] Test the " Andreas Philipp
2011-04-25 13:48     ` [PATCH 5/5] Updated documentation for btrfs subvolume snapshot Andreas Philipp
2011-04-26  5:42     ` [PATCH 0/5] Add user-space support for read-only snapshot creation Li Zefan
  -- strict thread matches above, loose matches on Subject: below --
2011-04-13  9:12 Andreas Philipp
2011-04-13  9:12 ` [PATCH 1/5] Add support for read-only subvolumes Andreas Philipp

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=1303773807-sup-7001@think \
    --to=chris.mason@oracle.com \
    --cc=kreijack@libero.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=philipp.andreas@gmail.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).