linux-kernel - Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing [try #13]

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1157607018.5929.8.camel@raven.themaw.net>
Date:	Thu, 07 Sep 2006 13:30:18 +0800
From:	Ian Kent <raven@...maw.net>
To:	David Howells <dhowells@...hat.com>
Cc:	Trond Myklebust <trond.myklebust@....uio.no>,
	Andrew Morton <akpm@...l.org>, torvalds@...l.org,
	steved@...hat.com, linux-fsdevel@...r.kernel.org,
	linux-cachefs@...hat.com, nfsv4@...ux-nfs.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7] Permit filesystem local caching and NFS superblock
	sharing [try #13]

On Wed, 2006-09-06 at 14:24 +0100, David Howells wrote:
> Trond Myklebust <trond.myklebust@....uio.no> wrote:
> 
> > It really doesn't matter whether there is a symlink or not. automounters
> > should _not_ be trying to create directories on any filesystem other
> > than the autofs filesystem itself.
> 
> Yes, I agree.

Not really.

What about multiple recursive bind mounts?
What about the initial directory for the autofs mount itself?

What about the case where a admin expects autofs to create these
directories for map entries that have multiple offsets.

As I've said before in version 5 I'm saying that it is a requirement
that the the directories already exist in this case but in version 4
people may have become accustomed to this behavior and right or wrong
this type of change shouldn't be made without warning to the users or
possibly not made at all.

Ian

-
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/