linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: "Misono, Tomohiro" <misono.tomohiro@jp.fujitsu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH v3 0/7] btrfs-progs: Allow normal user to call "subvolume list/show"
Date: Wed, 28 Mar 2018 09:45:11 -0400	[thread overview]
Message-ID: <20180328134501.GA2446@hungrycats.org> (raw)
In-Reply-To: <a1089ceb-6642-0b20-9690-6cf961efe42e@jp.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

On Mon, Mar 19, 2018 at 04:30:17PM +0900, Misono, Tomohiro wrote:
> This is a part of RFC I sent last December[1] whose aim is to improve normal users' usability.
> The remaining works of RFC are: 
>   - Allow "sub delete" for empty subvolume

I don't mean to scope creep on you, but I have a couple of wishes related
to this topic:

  - allow "rmdir" to remove an empty subvolume, i.e. when a subvolume is
    detected in rmdir, try switching to subvol delete before returning
    an error.  This lets admin tools that are not btrfs-aware do 'rm
    -fr' on a user directory when it contains a subvolume.  Legacy admin
    tools (or legacy tools in general) can't remove a subvol, and there
    is no solution for environments where we can't just fire users who
    create them.

  - mount option to restrict "sub create" and "sub snapshot" to root only.
    If we get "rmdir" working then this is significantly less important.

>   - Allow "qgroup show" to check quota limit
> 
> [1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg70991.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2018-03-28 13:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19  7:30 [RFC PATCH v3 0/7] btrfs-progs: Allow normal user to call "subvolume list/show" Misono, Tomohiro
2018-03-19  7:30 ` [RFC PATCH v3 1/7] btrfs-progs: sub list: Call rb_free_nodes() in error path Misono, Tomohiro
2018-03-19  7:31 ` [RFC PATCH v3 2/7] btrfs-progs: ioctl: Add 3 definitions of new unprivileged ioctl Misono, Tomohiro
2018-03-19  7:31 ` [RFC PATCH v3 3/7] btrfs-progs: sub list: Pass specified path down to btrfs_list_subvols() Misono, Tomohiro
2018-03-19  7:32 ` [RFC PATCH v3 4/7] btrfs-progs: fallback to open without O_NOATIME flag in find_mount_root() Misono, Tomohiro
2018-03-19  7:32 ` [RFC PATCH v3 5/7] btrfs-progs: sub list: Allow normal user to call "subvolume list/show" Misono, Tomohiro
2018-03-19 17:09   ` Goffredo Baroncelli
2018-03-20  1:41     ` Misono, Tomohiro
2018-03-19  7:33 ` [RFC PATCH v3 6/7] btrfs-progs: test: Add helper function to check if test user exists Misono, Tomohiro
2018-03-19  7:33 ` [RFC PATCH v3 7/7] btrfs-porgs: test: Add cli-test/009 to check subvolume list for both root and normal user Misono, Tomohiro
2018-03-28 13:45 ` Zygo Blaxell [this message]
2018-03-28 13:47   ` [RFC PATCH v3 0/7] btrfs-progs: Allow normal user to call "subvolume list/show" Zygo Blaxell
2018-03-29 17:35 ` Goffredo Baroncelli
2018-03-30  4:46   ` Misono Tomohiro
2018-03-30 16:16     ` Goffredo Baroncelli
2018-03-30 16:25     ` Goffredo Baroncelli

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=20180328134501.GA2446@hungrycats.org \
    --to=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=misono.tomohiro@jp.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).