From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mount --bind and -o [re: nosuid/noexec/nodev handling]
Date: Sun, 14 Oct 2001 20:09:57 +0300 [thread overview]
Message-ID: <20011014200957.S1074@niksula.cs.hut.fi> (raw)
In-Reply-To: <20011014191218.Q1074@niksula.cs.hut.fi> <Pine.GSO.4.21.0110141217000.6026-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0110141217000.6026-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Sun, Oct 14, 2001 at 12:20:34PM -0400
On Sun, Oct 14, 2001 at 12:20:34PM -0400, you [Alexander Viro] claimed:
>
>
> On Sun, 14 Oct 2001, Ville Herva wrote:
>
> > BTW, I just managed get a mount process to unkillable (-9) state while
> > playing with --bind. You might be uninterested in details if I can figure
> > out how to reproduce it?
>
> I would be _very_ interested in details. A word of warning, though -
> /proc/mounts is b0rken. If its output grows beyond 4Kb (no matter what
> had caused that - lots of NFS mounts, many bindings, etc.) it silently
> truncates the output. Result: deeply confused umount -a.
>
> I'll post the fix as soon as I finish it. For now too many mountpoints
> of any description == confused df and umount -a.
$ wc -c /proc/mounts
663 /proc/mounts
In this case the /proc/mounts seems not to be the problem. Also, mount out
put is sane and further mount commands succeed.
-- v --
v@iki.fi
next prev parent reply other threads:[~2001-10-14 17:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 15:59 Ville Herva
2001-10-14 16:06 ` Alexander Viro
2001-10-14 16:12 ` Ville Herva
2001-10-14 16:20 ` Alexander Viro
2001-10-14 17:09 ` Ville Herva [this message]
2001-10-14 17:23 ` Ville Herva
2001-10-14 17:32 ` Alexander Viro
2001-10-14 16:22 ` Ville Herva
2001-10-14 16:29 ` Alexander Viro
2001-10-14 17:44 ` Ville Herva
2001-10-14 23:37 ` Bernd Eckenfels
2001-10-14 23:48 ` Alexander Viro
2001-10-15 6:53 ` Ville Herva
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=20011014200957.S1074@niksula.cs.hut.fi \
--to=vherva@mail.niksula.cs.hut.fi \
--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®