public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: subvolume list as user?
Date: Sat, 16 Sep 2017 14:39:10 +0200	[thread overview]
Message-ID: <684fb723-4270-9589-b80b-e60ccc6dadfe@mendix.com> (raw)
In-Reply-To: <20170916094504.GL32347@rus.uni-stuttgart.de>

On 09/16/2017 11:45 AM, Ulli Horlacher wrote:
> Every user can create subvolumes (and root cannot prevent it!).
> But how can a user list these subvolumes?
> 
> tux@xerus:/test/tux: btrfs subvolume create test
> Create subvolume './test'

>From your other posts I don't quickly get if you actually do want to
have this possible, or accept that it's currently like that and try to
do damage control by having users also remove their things again.

Actually, if you don't want this I think it's quite easily to patch your
kernel with one or two lines of code to disallow it.

> tux@xerus:/test/tux: btrfs subvolume list .
> ERROR: can't perform the search - Operation not permitted

Yes, because the SEARCH ioctl only allows root to directly query any of
the filesystem metadata from kernel memory. subvolume list uses this
SEARCH ioctl to find it's info.

-- 
Hans van Kranenburg

  reply	other threads:[~2017-09-16 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16  9:45 subvolume list as user? Ulli Horlacher
2017-09-16 12:39 ` Hans van Kranenburg [this message]
2017-09-16 13:40   ` Hans van Kranenburg
2017-09-16 14:37   ` Ulli Horlacher
2017-09-16 20:56     ` Goffredo Baroncelli
2017-09-17  8:48       ` Ulli Horlacher

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=684fb723-4270-9589-b80b-e60ccc6dadfe@mendix.com \
    --to=hans.van.kranenburg@mendix.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