On Thu, 2007-08-30 at 20:49 -0700, Linus Torvalds wrote:It did not. The previous behaviour was to always silently override the user mount options. This is _not_ a kernel policy decision. The kernel is simply informing the user that it cannot fulfil the mount request as specified. Exactly why do you think that NFS should be any different from other filesystems when it comes to this? AFAIK, every other filesystem will give you an EBUSY if you try to mount a partition with -oro if you are already mounting somewhere else with -orw. Every filesystem will give you an EBUSY if you try to mount the partition with -oacl if it is mounted somewhere else with -onoacl. The reason: exactly the same as NFS, the caches cannot remain consistent when you try to mount two different super blocks that both refer to the same underlying filesystem. Trond -
| David Miller | Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. |
| Andrew Morton | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 010/196] Chinese: add translation of Codingstyle |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Felix von Leitner | socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0 |
git: | |
