From: Bart Noordervliet <bart@noordervliet.net>
To: Goffredo Baroncelli <goffredo.baroncelli@yahoo.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V3][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support
Date: Thu, 21 Mar 2013 16:27:02 +0100 [thread overview]
Message-ID: <CAGy7UthyO875AN1_GoeErfvssZVHOUxh58gdDgM_Ewc_JVPN5Q@mail.gmail.com> (raw)
In-Reply-To: <1362917859-18824-1-git-send-email-goffredo.baroncelli@yahoo.com>
Hi Goffredo,
On Sun, Mar 10, 2013 at 1:17 PM, Goffredo Baroncelli
<goffredo.baroncelli@yahoo.com> wrote:
> Unfortunately I noticed a regression which passed all the reviews until now:
> the command btrfs fi df previous didn't require the root capability,
> now with my patches it is required, because I need to know some info
> about the chunks so I need to use the "BTRFS_IOC_TREE_SEARCH".
>
> I think that there are the following possibilities:
> 1) accept this regresssion
> 2) remove the command "btrfs fi df" and leave only "btrfs fi disk-usage" and
> "btrfs dev disk-usage"
> 3) adding a new ioctl which could be used without root capability. Of course
> this ioctl would return only a subset of the BTRFS_IOC_TREE_SEARCH info
I'd like to vote for option 1) here. "btrfs fi df" gives useful,
condensed information that I can't get from the others at first
glance. I'd argue that many read-only, informational functions of the
btrfs utility already require root privileges even where that might
not be strictly necessary from a security point of view.
I'd also like to bump this thread in the hope that, if no one else
steps up with new, specific problems, we can now merge this patchset.
We can keep bikeshedding about the display details forever, but I
really think this is a significant improvement over what we had
previously.
Regards,
Bart
prev parent reply other threads:[~2013-03-21 15:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 12:17 [PATCH V3][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 1/8] Add some helpers to manage the strings allocation/deallocation Goffredo Baroncelli
2013-03-10 14:34 ` Wang Shilong
2013-03-10 14:51 ` Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 2/8] Enhance the command btrfs filesystem df Goffredo Baroncelli
2013-03-10 15:00 ` Wang Shilong
2013-03-10 12:17 ` [PATCH 3/8] Create the man page entry for the command btrfs fi df Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 4/8] Add helpers functions to handle the printing of data in tabular format Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 5/8] Add command btrfs filesystem disk-usage Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 6/8] Create entry in man page for " Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 7/8] Add btrfs device disk-usage command Goffredo Baroncelli
2013-03-10 12:17 ` [PATCH 8/8] Create a new entry in btrfs man page for btrfs device disk-usage Goffredo Baroncelli
2013-03-10 13:16 ` [PATCH V3][BTRFS-PROGS] Enhance btrfs fi df with raid5/6 support Martin Steigerwald
2013-03-10 13:19 ` Martin Steigerwald
2013-03-10 15:59 ` Goffredo Baroncelli
2013-03-10 15:52 ` Goffredo Baroncelli
2013-03-21 15:27 ` Bart Noordervliet [this message]
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=CAGy7UthyO875AN1_GoeErfvssZVHOUxh58gdDgM_Ewc_JVPN5Q@mail.gmail.com \
--to=bart@noordervliet.net \
--cc=goffredo.baroncelli@yahoo.com \
--cc=linux-btrfs@vger.kernel.org \
/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).