From: Al Viro <viro@ZenIV.linux.org.uk>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Eric Sandeen <sandeen@redhat.com>,
fsdevel <linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH 1/2 V2] fs: hoist BTRFS_IOC_[SG]ET_FSLABEL to vfs
Date: Thu, 10 May 2018 20:16:09 +0100 [thread overview]
Message-ID: <20180510191608.GR30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4a4f33c3-2173-9795-f4e4-1e9d338fd9a7@sandeen.net>
On Thu, May 10, 2018 at 01:13:57PM -0500, Eric Sandeen wrote:
> Move the btrfs label ioctls up to the vfs for general use.
>
> This retains 256 chars as the maximum size through the interface, which
> is the btrfs limit and AFAIK exceeds any other filesystem's maximum
> label size.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
> Reviewed-by: David Sterba <dsterba@suse.com>
No objections (and it obviously ought to go through btrfs tree).
next prev parent reply other threads:[~2018-05-10 19:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 15:56 [PATCH 0/2] hoist btrfs' label set/get ioctls to vfs, and document Eric Sandeen
2018-05-09 16:01 ` [PATCH 1/2] fs: hoist BTRFS_IOC_[SG]ET_FSLABEL to vfs Eric Sandeen
2018-05-09 16:10 ` Darrick J. Wong
2018-05-09 17:15 ` Andreas Dilger
2018-05-09 17:26 ` Darrick J. Wong
2018-05-09 17:35 ` Randy Dunlap
2018-05-09 17:40 ` Eric Sandeen
2018-05-09 21:35 ` David Sterba
2018-05-10 18:13 ` [PATCH 1/2 V2] " Eric Sandeen
2018-05-10 19:16 ` Al Viro [this message]
2018-05-11 14:10 ` David Sterba
2018-05-11 14:32 ` [PATCH 1/2 V2] " Chris Mason
2018-05-11 14:36 ` Eric Sandeen
2018-05-11 14:41 ` David Sterba
2018-05-12 0:20 ` Darrick J. Wong
2018-05-09 16:04 ` [PATCH 2/2] man2: New page documenting filesystem get/set label ioctls Eric Sandeen
2018-05-09 16:15 ` Darrick J. Wong
2018-05-10 17:29 ` [PATCH 2/2 V2] " Eric Sandeen
2018-05-10 17:35 ` Eric Sandeen
2020-04-20 12:04 ` Michael Kerrisk (man-pages)
2020-04-20 13:48 ` Eric Sandeen
2020-04-20 15:29 ` Michael Kerrisk (man-pages)
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=20180510191608.GR30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=sandeen@sandeen.net \
/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).