From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: deleting files and qgroups
Date: Mon, 27 Jan 2014 08:50:06 +0000 (UTC) [thread overview]
Message-ID: <pan$37643$969fc17b$d862cdfc$854e4085@cox.net> (raw)
In-Reply-To: 6820542.RmHzTAgQHU@russell.coker.com.au
Russell Coker posted on Mon, 27 Jan 2014 18:59:16 +1100 as excerpted:
> As an aside, is it expected that a SE Linux Play Machine (with hostile
> "root" user) should survive with BTRFS? I'm preparing a new Play
> Machine which will run BTRFS and use qgroups, are there any bugs or
> missing features I should be aware of?
>
> I realise that qgroups are an area of BTRFS that hasn't been tested a
> lot and that using them to restrict actively hostile users is probably
> more experimental than most BTRFS stuff. But I'm happy to get a broken
> system if we learn something useful.
While (as a btrfs user not dev) I don't use qgroups here, AFAIK, they
have known bugs ATM and are not considered ready for primetime. Among
other infamous current bugs, deleting subvolumes with qgroups enabled can
lead to negative quotas as that bit simply isn't managed properly at all!
At this point, therefore, I'd not only not recommend depending on qgroups
at all, I'd recommend not even trying to test them unless you're actively
working on the currently known bugs, as there's simply too much /known/
wrong with them ATM to sanely test, unless you're close enough to
development to know what's a known bug that they're already working on
fixing and what's not.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-01-27 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 7:59 deleting files and qgroups Russell Coker
2014-01-27 8:50 ` Duncan [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='pan$37643$969fc17b$d862cdfc$854e4085@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).