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: Thu, 13 Nov 2008 12:57:11 +0100 From: Miklos Szeredi <miklos@...redi.hu> To: tj@...nel.org CC: miklos@...redi.hu, fuse-devel@...ts.sourceforge.net, greg@...ah.com, linux-kernel@...r.kernel.org Subject: Re: [PATCHSET] FUSE: extend FUSE to support more operations On Thu, 13 Nov 2008, Tejun Heo wrote: > I don't really mind people doing strange things in userland as long as > it's safe but you're the maintainer. It's a bit strange to export the > feature only for CUSE, so I'm a little bit hesitant. You are starting from the fact that ioctl is a good API. It's not, it's a bad API, so I don't want to encourage the use of it. > I wanna make it > useful for both. So, at the kernel level, only well formed for FUSE and > everything goes for CUSE. Does that sound good enough? With additional restrictions for ptraceability yes. But if you just restrict it to CUSE at first, that's fine by me as well :) Thanks, Miklos -- 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