| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1189007414.13235.20.camel@gaula.trondhjem.org> Date: Wed, 05 Sep 2007 16:50:14 +0100 From: Trond Myklebust <trond.myklebust@....uio.no> To: David Howells <dhowells@...hat.com> Cc: Ian Kent <raven@...maw.net>, Bill Davidsen <davidsen@....com>, Linus Torvalds <torvalds@...ux-foundation.org>, Frank van Maarseveen <frankvm@...nkvm.com>, Hua Zhong <hzhong@...il.com>, 'Linux Kernel Mailing List' <linux-kernel@...r.kernel.org>, akpm@...ux-foundation.org Subject: Re: recent nfs change causes autofs regression On Wed, 2007-09-05 at 16:37 +0100, David Howells wrote: > Ian Kent <raven@...maw.net> wrote: > > > But what about mounting with different protocol, tcp vs udp for example. > > I was referring specifically to the R/O / R/W variants of the same mount. Any > flag variation that varies the way the NFS client talks to the NFS server must > either result in a new superblock or be ignored. > > David We currently ignore remount requests that attempt to change the NFS mount parameters. This is not new behaviour, BTW: it has always been the case, and nobody has ever requested it. The ro flag is different, and I agree that it should be moved to the vfsmount structure. I'm hoping Dave Hansen's patches will be ready for merging soon... Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists