linux-kernel - Re: VFS + path walktrough

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:	Mon, 05 May 2008 19:03:33 +0200
From:	Miklos Szeredi <miklos@...redi.hu>
To:	miklos@...redi.hu
CC:	viro@...IV.linux.org.uk, weigelt@...ux.de,
	linux-kernel@...r.kernel.org
Subject: Re: VFS + path walktrough

> > > * Al Viro <viro@...IV.linux.org.uk> wrote:
> > > > That you have quite forgotten about mounts.  
> > > 
> > > hmm, I though this would be done before the link_path_walk() 
> > > call happens ;-o
> > 
> > How on the earth...?  You don't know where will pathname resolution
> > get you, so how could you possibly handle mountpoint transitions prior
> > to it?
> 
> One way this could be done cleanly, is to pass the rest of the path
> (as hint) to the filesystem in its lookup function.  Most filesystems
> would just ignore it, but those which have the capabilities can use it
> to do the lookup in one go, and internally

Better, the filesystem can just populate the dcache with the result.
The entry being looked up is locked, so noone can get at it, and so it
should be quite safe to build a tree below.

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