| 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
| ||
|
Date: Mon, 5 May 2008 20:23:09 +0200 From: Enrico Weigelt <weigelt@...ux.de> To: linux kernel list <linux-kernel@...r.kernel.org> Subject: Re: VFS + path walktrough * Al Viro <viro@...IV.linux.org.uk> wrote: > > 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... I've just read the spec for walk again: Assuming the server doesn't resolve symlinks itself, the walk will fail right at the symlink. So we can have a deeper look here and try stat()'ing (adds one more request). If the fail point *is* an symlink, we need to properly handle it. Would it be very complicated to give the link target back to VFS and let the lookup start again (w/ new name) ? > 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... Naive question: is it really *necessary* to have all the intermediate dirs in dcache ? cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- 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