| 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: Wed, 17 Jun 2009 19:52:19 +0100 From: Al Viro <viro@...IV.linux.org.uk> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Andreas Dilger <adilger@....com>, David Howells <dhowells@...hat.com>, Alan Cox <alan@...rguk.ukuu.org.uk>, akpm@...ux-foundation.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, linux-afs@...ts.infradead.org Subject: Re: [PATCH 00/17] [RFC] AFS: Implement OpenAFS pioctls(version)s On Wed, Jun 17, 2009 at 11:44:18AM -0700, Linus Torvalds wrote: > > O_NOFOLLOW *will* open their mountpoints just fine, without triggering > > automount. > > That's not the problem with O_NOFOLLOW. > > The problem is that if you want to actually open the symlink itself (say, > you do some filesystem cleanup operation on it, like saying "drop the > caches of this file"), you can't do it. O_NOFOLLOW won't open the symlink, > it will just refuse to follow it, and return an error. ... so we need a syscall that would do that "drop the caches" operation. _After_ having decided that it's really needed for symlinks. With decision made on per-operation basis. Sure, it will be painful for people proposing such operations, which is just fine by me - barriers to adding new primitives shouldn't be low. -- 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