From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mike Galbraith <efault@gmx.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Martin Knoblauch <knobi@knobisoft.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org,
tigran aivazian <tigran@aivazian.fsnet.co.uk>
Subject: Re: Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow
Date: Wed, 29 Apr 2009 15:34:03 +0100 [thread overview]
Message-ID: <20090429143403.GJ8633@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1241014725.15095.19.camel@marge.simson.net>
On Wed, Apr 29, 2009 at 04:18:45PM +0200, Mike Galbraith wrote:
> > /etc/fstab, perhaps? That definitely looks like two mount(2) had to
> > have been done to cause that...
>
> Yeah, but how does one go about doing that?
>
> Using mount -f, I can convince mount to succeed, but I still have only
> one entry in /proc/mounts, despite what my mount binary imagines.
Huh?
-f Causes everything to be done except for the actual system call;
if it's not obvious, this ``fakes'' mounting the file system.
This option is useful in conjunction with the -v flag to deter-
mine what the mount command is trying to do. It can also be used
to add entries for devices that were mounted earlier with the -n
What are you talking about?
The interesting part is why mount(2) doesn't fail with -EBUSY on that
overmounting. Is there anything else mounted on /sys? That, or any
interesting patches applied to the tree (fs/sysfs/mount.c, fs/namespace.c)
next prev parent reply other threads:[~2009-04-29 14:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 12:45 Analyzed/Solved: Booting 2.6.30-rc2-git7 very slow Martin Knoblauch
2009-04-29 1:28 ` Andrew Morton
2009-04-29 3:51 ` Mike Galbraith
2009-04-29 8:17 ` Andrew Morton
2009-04-29 9:36 ` Martin Knoblauch
2009-04-29 9:45 ` Martin Knoblauch
2009-04-29 12:08 ` Al Viro
2009-04-29 14:18 ` Mike Galbraith
2009-04-29 14:34 ` Al Viro [this message]
2009-04-29 17:28 ` Martin Knoblauch
2009-04-29 19:11 ` Mike Galbraith
2009-05-05 22:49 ` Andrew Morton
2009-05-06 4:45 ` Mike Galbraith
2009-05-06 7:55 ` Martin Knoblauch
2009-05-06 8:37 ` Mike Galbraith
2009-05-06 10:57 ` Martin Knoblauch
2009-05-20 10:22 ` Analyzed/Solved/Bisected: " Martin Knoblauch
2009-05-27 6:31 ` Andrew Morton
2009-05-27 9:14 ` Martin Knoblauch
2009-05-27 11:21 ` Matthew Wilcox
2009-05-27 11:53 ` Martin Knoblauch
2009-05-27 18:07 ` jim owens
2009-05-27 18:18 ` Miller, Mike (OS Dev)
2009-05-27 20:12 ` jim owens
2009-05-27 21:18 ` Miller, Mike (OS Dev)
2009-05-28 8:59 ` Martin Knoblauch
2009-05-28 19:01 ` Miller, Mike (OS Dev)
2009-05-28 20:48 ` Martin Knoblauch
2009-04-29 17:24 ` Analyzed/Solved: " Martin Knoblauch
2009-04-29 17:35 ` Valdis.Kletnieks
2009-04-29 17:43 ` Al Viro
2009-04-30 13:02 ` Olivier Galibert
2009-04-29 17:45 ` Martin Knoblauch
2009-04-29 17:41 ` Al Viro
2009-04-29 17:51 ` Martin Knoblauch
2009-04-29 18:10 ` Al Viro
2009-04-30 9:12 ` Martin Knoblauch
2009-05-27 6:22 ` Andrew Morton
2009-04-29 9:34 ` Martin Knoblauch
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=20090429143403.GJ8633@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=knobi@knobisoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tigran@aivazian.fsnet.co.uk \
/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