From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, viro@math.psu.edu
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: mount --bind accounting
Date: Mon, 4 Jun 2001 02:59:34 +0200 (MET DST) [thread overview]
Message-ID: <UTC200106040059.CAA184232.aeb@vlet.cwi.nl> (raw)
>> /* No capabilities? What if users do thousands of these? */
> look at mount_is_safe()
Yes, good. My remark means that more tests are required
than those sketched in mount_is_safe(), and that means
that for the time being we can throw out the routine
mount_is_safe(), and remove the test on capable(CAP_SYS_ADMIN)
in do_remount(), and move the same test in do_mount up to
the start: all forms of mount require CAP_SYS_ADMIN.
[side effect: remount read-only upon umount of root fs
may be possible in a few more cases]
Andries
next reply other threads:[~2001-06-04 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 0:59 Andries.Brouwer [this message]
2001-06-04 1:11 ` mount --bind accounting Alexander Viro
-- strict thread matches above, loose matches on Subject: below --
2001-06-03 20:38 Andries.Brouwer
2001-06-04 0:18 ` Alexander Viro
2001-06-06 18:20 ` Stephen C. Tweedie
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=UTC200106040059.CAA184232.aeb@vlet.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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