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, 5 May 2008 18:40:48 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Miklos Szeredi <miklos@...redi.hu>
Cc:	weigelt@...ux.de, linux-kernel@...r.kernel.org
Subject: Re: VFS + path walktrough

On Mon, May 05, 2008 at 07:33:00PM +0200, Miklos Szeredi wrote:

> > This is still wrong.  We not just pass the pathname to filesystem (note
> > that you still need to deal with symlinks),
> 
> Symlinks are easy: filesystem just needs to *stop* the resolution the
> moment it finds one.

That assumes you see types of objects as you do multi-step walk...

> >  Take a look at 9P walk - it does *not* give
> > you anything resembling stat, you just get qids of intermediates.
> 
> Which is exactly what's needed to populate the dentry tree, no?

No - you need inodes as well (i.e. as the absolute least you want
mode and ownership).  Which is to say, you need to issue stat on
each component in such situation anyway.  Not a win...
--
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/