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 14:13:08 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Enrico Weigelt <weigelt@...ux.de>
Cc:	linux kernel list <linux-kernel@...r.kernel.org>
Subject: Re: VFS + path walktrough

On Mon, May 05, 2008 at 03:06:23PM +0200, Enrico Weigelt wrote:

> We could just add another call vector to struct file_operations,
> as replacement for link_path_walk() - if it's zero, the original
> function is used. This way an filesystem can do the walktrough
> by it's own, but doesn't need to.
> 
> 
> What do you think about this ?

That you have quite forgotten about mounts.  And we *REALLY* don't
want to shift the entire logics of link_path_walk() into filesystems -
this is insane.  Even "let's follow that symlink" part alone, not to
mention mountpoint handling, populating dcache, etc.
--
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/