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 01:25:58 +0100 From: David Howells <dhowells@...hat.com> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: dhowells@...hat.com, torvalds@...l.org, 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 Alan Cox <alan@...rguk.ukuu.org.uk> wrote: > But if we add an ABI we end up stuck with it and this one is really > really rather ugly. Somewhat less ugly than ioctl, for instance, but you're not entirely wrong. There is no good way of doing this. > Can you not put pioctl() into a C library linked with the openafs utilities > that generates more sensible interface calls? I mean you have to produce > the pioctl() syscall wrapper anyway so why not make "pioctl" a user space > compat library? pioctl() is almost implementable with a combination of (l)setxattr, (l)getxattr, set_key, keyctl_read, and if all else fails, open + ioctl or open(O_NOFOLLOW) + ioctl, but not quite completely. There are things you can't open, even with O_NOFOLLOW. And doing state-retaining setxattr/getxattr pairs is even more nasty than pioctl (IIRC, that's something Christoph suggested a while back). Besides, I want a set of utilities that I can use in conjunction with both kAFS and OpenAFS without having to recompile. David -- 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