mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Felix Braun <Felix.Braun@mail.McGill.ca>
Cc: viro@math.psu.edu, linux-kernel@vger.kernel.org
Subject: Re: devfs mounted twice in linux 2.4.19-pre3
Date: Tue, 19 Mar 2002 23:30:23 -0700	[thread overview]
Message-ID: <200203200630.g2K6UNw24115@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20020317121954.390bc242.Felix.Braun@mail.McGill.ca>

Felix Braun writes:
> Hi Richard,
> 
> I just noticed that devfs is listed twice in /proc/mounts in linux
> 2.4.19-pre3, which confuses my shutdown script. Under 2.4.19-pre my
> /proc/mounts looks like this:
> 
> devfs /dev devfs rw 0 0
> /dev/ide/host0/bus0/target0/lun0/part5 / reiserfs rw 0 0
> none /dev devfs rw 0 0
> /proc /proc proc rw 0 0
> /dev/discs/disc0/part1 /dos vfat rw 0 0
> /dev/discs/disc0/part9 /opt reiserfs rw,noatime 0 0
> none /dev/pts devpts rw 0 0
> /dev/discs/disc0/part7 /usr reiserfs rw 0 0
> none /dev/shm tmpfs rw 0 0
> 
> whereas under 2.4.18 the first line didn't show up. Is that a
> misconfiguration on my part?

No, this is due to a change in the kernel (presumably done by Al).
What seems to be happening is that the kernel temporarily mounts devfs
and then detaches it again using MNT_DETACH (actually, you need
2.4.19-pre3-ac2 to get the fix that adds MNT_DETACH). However,
detached filesystems still appear to be listed in /proc/mounts.
Arguably, this is incorrect.

If you were to reboot single-user, and with devfs=nomount, inspection
of /proc/mounts would show the line:
devfs /dev devfs rw 0 0

However, if you listed /dev, you would see that it doesn't actually
contain a devfs. Thus, /proc/mounts is deceiving you.

Al: what is the intended behaviour of MNT_DETACH wrt. /proc/mounts?

				Regards,

					Richard....
Permanent: rgooch@atnf.csiro.au
Current:   rgooch@ras.ucalgary.ca

  parent reply	other threads:[~2002-03-20  6:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-17 11:19 Felix Braun
2002-03-18 10:39 ` Denis Vlasenko
2002-03-18 12:38   ` Paul P Komkoff Jr
2002-03-18 15:36   ` Richard Gooch
2002-03-18 15:58     ` Alexander Viro
2002-03-18 16:08       ` Richard Gooch
2002-03-20  6:30 ` Richard Gooch [this message]
2002-03-25  0:08   ` Richard Gooch
     [not found]     ` <200203250852.g2P8qr503025@ns.caldera.de>
     [not found]       ` <200203251658.g2PGwf228854@vindaloo.ras.ucalgary.ca>
2002-03-25 17:06         ` 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=200203200630.g2K6UNw24115@vindaloo.ras.ucalgary.ca \
    --to=rgooch@ras.ucalgary.ca \
    --cc=Felix.Braun@mail.McGill.ca \
    --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

all inboxes | Powered by JetHome®