From: Nicholas D Steeves <nsteeves@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: user_subvol_rm_allowed? Is there a user_subvol_create_deny|allowed?
Date: Tue, 7 Feb 2017 20:49:31 -0500 [thread overview]
Message-ID: <20170208014931.GA22397@DigitalMercury.dynalias.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1251 bytes --]
Dear btrfs community,
Please accept my apologies in advance if I missed something in recent
btrfs development; my MUA tells me I'm ~1500 unread messages
out-of-date. :/
I recently read about "mount -t btrfs -o user_subvol_rm_allowed" while
doing reading up on LXC handling of snapshots with the btrfs backend.
Is this mount option per-subvolume, or per volume?
Also, what mechanisms to restrict a user's ability to create an
arbitrarily large number of snapshots? Is there a
user_subvol_create_deny|allowed? What I've read about the inverse
correlation between number of subvols to performance, a potentially
hostile user could cause an IO denial of service or potentially even
trigger an ENOSPC.
From what I gather, the following will reproduce the hypothetical
issue related to my question:
# as root
btrfs sub create /some/dir/subvol
chown some-user /some/dir/subvol
# as some-user
cd /home/dir/subvol
cp -ar --reflink=always /some/big/files ./
COUNT=1
while [ 0 -lt 1 ]; do
btrfs sub snap ./ ./snapshot-$COUNT
COUNT=COUNT+1
sleep 2 # --maybe unnecessary
done
--
I hope there's something I've misunderstood or failed to read!
Please CC me so your reply will hit my main inbox :-)
Nicholas
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2017-02-08 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 1:49 Nicholas D Steeves [this message]
2017-02-08 12:26 ` user_subvol_rm_allowed? Is there a user_subvol_create_deny|allowed? Austin S. Hemmelgarn
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=20170208014931.GA22397@DigitalMercury.dynalias.net \
--to=nsteeves@gmail.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).