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: <1157460472.5621.3.camel@localhost>
Date:	Tue, 05 Sep 2006 08:47:52 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	David Howells <dhowells@...hat.com>
Cc:	Ian Kent <raven@...maw.net>, 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 Tue, 2006-09-05 at 10:57 +0100, David Howells wrote:
> Trond Myklebust <trond.myklebust@....uio.no> wrote:
> 
> > Why the hell is it doing a mkdir in the first place?
> 
> I think the problems it is solving are these:
> 
>  (1) What happens if "/" is _not_ exported?
> 
>  (2) What happens if some intermediate directory (say "/usr") is not
>      accessible?
> 
> 
> In the first case, the automounter just makes "usr" and "usr/src", say, in the
> autofs filesystem, and then mounts server:/usr/src on that.

That is fine. As long as it is doing so in the _autofs_ filesystem. A
call to 'stat()' should suffice to tell if this is the case.

> In the second case, the automounter relies on NFS letting it make intervening
> directories it couldn't otherwise access to span the gap between "/" and
> "src".

If the directory isn't accessible, then autofs shouldn't be trying to
override that. It certainly shouldn't be doing so by trying to create
the directory.

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ