All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org,
	Chris Mason <chris.mason@oracle.com>,
	lizf@cn.fujitsu.com
Subject: Re: [PATCH] Btrfs-progs: added btrfs filesystem label [label] [path] support V2
Date: Mon, 05 Sep 2011 13:34:46 +0800	[thread overview]
Message-ID: <4E645F76.5040505@oracle.com> (raw)
In-Reply-To: <20110904170301.GE9907@carfax.org.uk>

On 09/05/2011 01:03 AM, Hugo Mills wrote:
> On Sat, Sep 03, 2011 at 11:11:36AM +0800, Jeff liu wrote:
>> =E5=9C=A8 2011-9-2=EF=BC=8C=E4=B8=8B=E5=8D=8811:48=EF=BC=8C David St=
erba =E5=86=99=E9=81=93=EF=BC=9A
>>> On Fri, Sep 02, 2011 at 09:13:34PM +0800, Jeff Liu wrote:
>>>> --- a/ioctl.h
>>>> +++ b/ioctl.h
>>>> @@ -140,6 +140,8 @@ struct btrfs_ioctl_space_args {
>>>>                     struct btrfs_ioctl_vol_args)
>>>> #define BTRFS_IOC_SCAN_DEV _IOW(BTRFS_IOCTL_MAGIC, 4, \
>>>>                     struct btrfs_ioctl_vol_args)
>>>> +#define BTRFS_IOC_FS_SETLABEL _IOW(BTRFS_IOCTL_MAGIC, 5, \
>>>> +                   struct btrfs_ioctl_fs_label_args)
>>>> /* trans start and trans end are dangerous, and only for
>>>>   * use by applications that know how to avoid the
>>>>   * resulting deadlocks
>>> well, it is an unassigned number, but a newly added features should=
 IMHO
>>> allocate greater than current max value, ie over 31 in coordination=
 with
>>>
>>> https://btrfs.wiki.kernel.org/index.php/Project_ideas#Development_n=
otes.2C_please_read
>>>
>>> table.
>> It sounds reasonable to allocate a greater value, could anyone pleas=
e confirm it?
>     I'd just take number 50 for yours -- Li can update his patches
> later.
Thank you, I'll post a patch for this change later.

-Jeff
>     Hugo.
>
>> What's your ioctl range for online fsck?

--
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

  parent reply	other threads:[~2011-09-05  5:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01  8:52 [PATCH] Btrfs-progs: added btrfs filesystem label [label] [path] support Jeff Liu
2011-09-01 11:52 ` [PATCH] Btrfs-progs: added btrfs filesystem label [label] [path] support V2 Jeff Liu
2011-09-02 12:52   ` David Sterba
2011-09-02 13:13     ` Jeff Liu
2011-09-02 15:48       ` David Sterba
2011-09-03  3:11         ` Jeff liu
     [not found]           ` <20110904170301.GE9907@carfax.org.uk>
2011-09-05  5:34             ` Jeff Liu [this message]
2011-09-05  7:32               ` [PATCH] Btrfs-progs: added btrfs filesystem label [label] [path] support V3 Jeff Liu
2011-09-05  7:30             ` [PATCH] Btrfs: added new ioctl to set fs label V3 Jeff Liu

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=4E645F76.5040505@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=chris.mason@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lizf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.