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...)
Attachment:
pgpwbjgx5nOeD.pgp
Description: PGP signature
- Follow-Ups:
- Re: 2.6.17-rc3 - fs/namespace.c issue
- From: Andrew Morton <[email protected]>
- Re: 2.6.17-rc3 - fs/namespace.c issue
- Prev by Date: [patch 2.6.17-rc3] smsc-ircc2, minimal PNP hotplug support
- Next by Date: Re: [PATCH] CodingStyle: add typedefs chapter
- Previous by thread: [patch 2.6.17-rc3] smsc-ircc2, minimal PNP hotplug support
- Next by thread: Re: 2.6.17-rc3 - fs/namespace.c issue
- Index(es):