public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Valdis.Kletnieks@vt.edu, torvalds@osdl.org,
	linux-kernel@vger.kernel.org, herbert@13thfloor.at, hch@lst.de
Subject: Re: 2.6.17-rc3 - fs/namespace.c issue
Date: Fri, 12 May 2006 11:09:03 -0700	[thread overview]
Message-ID: <20060512110903.4d76b191.akpm@osdl.org> (raw)
In-Reply-To: <1147456936.23563.73.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
> On Fri, 2006-05-12 at 10:53 -0700, Andrew Morton wrote:
> > Stephen Smalley <sds@tycho.nsa.gov> wrote:
> > >
> > > On Mon, 2006-05-01 at 14:33 -0700, Andrew Morton wrote:
> > > > Valdis.Kletnieks@vt.edu wrote:
> > > > >
> > > > > There seems to have been a bug introduced in this changeset:
> > > > > 
> > > > > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=f6422f17d3a480f21917a3895e2a46b968f56a08
> > > > > 
> > > > > Am running 2.6.17-rc3-mm1.  When this changeset is applied, 'mount --bind'
> > > > > misbehaves:
> > > > > 
> > > > > > # mkdir /foo
> > > > > > # mount -t tmpfs -o rw,nosuid,nodev,noexec,noatime,nodiratime none /foo
> > > > > > # mkdir /foo/bar
> > > > > > # mount --bind /foo/bar /foo
> > > > > > # tail -2 /proc/mounts
> > > > > > none /foo tmpfs rw,nosuid,nodev,noexec,noatime,nodiratime 0 0
> > > > > > none /foo tmpfs rw 0 0
> > > > > 
> > > > > Reverting this changeset causes both mounts to have the same options.
> > > > > 
> > > > > (Thanks to Stephen Smalley for tracking down the changeset...)
> > > > > 
> > > > 
> > > > (cc's added)
> > > 
> > > What's the verdict on this change in user-visible behavior for bind
> > > mounts?  Is it a legitimate change and userland just needs to adapt to
> > > it, or is it a change to the kernel's stable ABI that needs to be
> > > reverted?  It still appears to be present in -rc4.
> > > 
> > 
> > Well.  We'd certainly prefer to not change user-visible behaviour without
> > excellent reasons - I don't htink any have been given, really.
> > 
> > AFACIT nobody tested Herbert's 'untested "fix"'.  What was the verdict on
> > that?
> 
> The untested 'fix' makes the rest of the patch pointless (no point in
> passing the mnt_flags if we aren't going to use them).  Might as well
> just revert the patch altogether.

OK, I queued a revert.  It seems to be the sanest thing to do at this time
- Herbert can have another go later..

  reply	other threads:[~2006-05-12 18:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-01 21:06 2.6.17-rc3 - fs/namespace.c issue Valdis.Kletnieks
2006-05-01 21:33 ` Andrew Morton
2006-05-01 23:56   ` Herbert Poetzl
2006-05-02  6:56     ` Valdis.Kletnieks
2006-05-02 16:48       ` Herbert Poetzl
2006-05-15 21:18     ` Bill Davidsen
2006-05-12 17:36   ` Stephen Smalley
2006-05-12 17:53     ` Andrew Morton
2006-05-12 18:02       ` Stephen Smalley
2006-05-12 18:09         ` Andrew Morton [this message]
2006-05-13 13:54           ` Herbert Poetzl

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=20060512110903.4d76b191.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=hch@lst.de \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=torvalds@osdl.org \
    /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