From: Jeff Garzik <jgarzik@pobox.com>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Alexander Viro <viro@math.psu.edu>, linux-kernel@vger.kernel.org
Subject: Re: rootfs exposure in /proc/mounts
Date: Sat, 26 Oct 2002 15:26:49 -0400 [thread overview]
Message-ID: <3DBAEC79.5050605@pobox.com> (raw)
In-Reply-To: 3DBAE931.7000409@domdv.de
Andreas Steinmetz wrote:
> Alexander Viro wrote:
>
>>
>> On Sat, 26 Oct 2002, Andreas Steinmetz wrote:
>>
>>
>>> Maybe I do oversee the obious but:
>>>
>>> can somebody please explain why rootfs is exposed in /proc/mounts (I
>>> do mean the "rootfs / rootfs rw 0 0" entry) and if there is a good
>>> reason for the exposure?
>>
>>
>>
>> Mostly the fact that it _is_ mounted and special-casing its removal from
>> /proc/mounts is more PITA than it's worth.
>>
> Acceptable but somewhat sad as it confuses e.g. "umount -avt noproc"
> which is somewhat standard in shutdown/reboot scripts (using a
> softlink from /etc/mtab to /proc/mounts).
Bug 1 - don't softlink directly to /proc/mounts :) embedded guys
typically do this, and you see why it bites you in the ass :)
Bug 2 - "noproc" clearly does not avoid ramfs mounts, which is rootfs's
filesystem type. And more and more ramfs filesystems will be appearing,
so that should be taken into consideration.
Sounds like userspace slackness to me, and nothing that the kernel guys
need to worry about...
Jeff
next prev parent reply other threads:[~2002-10-26 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 18:53 rootfs exposure in /proc/mounts Andreas Steinmetz
2002-10-26 18:59 ` Alexander Viro
2002-10-26 19:12 ` Andreas Steinmetz
2002-10-26 19:26 ` Jeff Garzik [this message]
2002-10-27 0:22 ` Andreas Steinmetz
2002-10-27 10:21 ` Andreas Haumer
2002-10-27 11:18 ` Willy Tarreau
2002-10-27 23:27 ` Michal Jaegermann
2002-10-28 9:05 ` Kasper Dupont
2002-10-27 15:02 ` Jeff Garzik
2002-10-27 15:09 ` Christoph Hellwig
2002-10-28 0:03 ` Kenneth Johansson
2002-10-28 0:18 ` Christoph Hellwig
2002-10-28 1:17 ` Rob Landley
2002-10-28 15:01 ` Christoph Hellwig
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=3DBAEC79.5050605@pobox.com \
--to=jgarzik@pobox.com \
--cc=ast@domdv.de \
--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