| 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: Fri, 29 Aug 2008 21:47:26 +0200 From: Arnd Bergmann <arnd@...db.de> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: Tejun Heo <tj@...nel.org>, Miklos Szeredi <miklos@...redi.hu>, Serge Hallyn <serue@...ibm.com>, greg@...ah.com, fuse-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH 5/7] FUSE: implement ioctl support On Friday 29 August 2008, Eric W. Biederman wrote: > However it is a largely an insane idea. I fully agree. > Given the pain it is to maintain ioctls I would be very surprised if we wanted > to open up that pandoras box even wider by allowing arbitrary user space > processes to support random ioctls. How would you do 32/64bit support > and the like? I think that is not too much of a problem: Just like the file operations in the kernel have two callbacks (ioctl and compat_ioctl), you need to provide both operations from user space if there is a difference between them, or at least a stub otherwise. Arnd <>< -- 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