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]

Date:	Wed, 06 Sep 2006 10:51:46 +0100
From:	David Howells <dhowells@...hat.com>
To:	Ian Kent <raven@...maw.net>
Cc:	David Howells <dhowells@...hat.com>,
	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] 

Ian Kent <raven@...maw.net> wrote:

> > Not if you've already caused the NFS filesystem to create a "dummy" dentry
> > that's a directory because you couldn't see that what that name
> > corresponds to on the server is actually a symlink.
> 
> Shouldn't stat tell me if this is a symlink?

You may not be able to find out from the server what it is you're trying to
deal with because you may not have permission to do so, or because whatever it
is may not be exported.  The first may be the trickiest to deal with because
the MOUNT service for NFS2 and NFS3 can jump you over bits of the path you
can't otherwise access.

The problem actually comes when the conditions on the server change; perhaps an
intermediate directory is made accessible on the server and suddenly the client
can see inside of it.  It may then find out that what it had assumed to be
directories, and what it had set dummy directory dentries up for, aren't.

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