From: Christoph Hellwig <hch@infradead.org>
To: Sage Weil <sage@newdream.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: 'usertrans' mount option to allow unprivileged userspace transactions
Date: Fri, 26 Jun 2009 13:09:44 -0400 [thread overview]
Message-ID: <20090626170944.GB2412@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0906221434150.9993@cobra.newdream.net>
On Thu, Jun 25, 2009 at 02:45:39PM -0700, Sage Weil wrote:
> This lets an administrator give non-root users access to the btrfs
> transaction start/end ioctls via a mount option.
>
> Currently any process using the ioctls must run as root. That's
> appropriate in general, since the ioctls allow let any process to hang fs
> commits by holding an open transaction indefinitely. But on locked down
> hosts (i.e. no users), that can be inconvenient because daemons using
> transactions have to run as root.
If the system is locked down there is no problem giving the capability
to the daemon user. I'm strong against adding any kind of
privilegue-evading options to filesystems.
next prev parent reply other threads:[~2009-06-26 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 21:45 [PATCH] btrfs: 'usertrans' mount option to allow unprivileged userspace transactions Sage Weil
2009-06-26 17:09 ` Christoph Hellwig [this message]
2009-06-29 16:40 ` Sage Weil
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=20090626170944.GB2412@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.net \
/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