| 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
| ||
|
Message-Id: <1217714096.6280.35.camel@kokopelli> Date: Sat, 02 Aug 2008 14:54:56 -0700 From: Brian Beattie <beattie@...ttie-home.net> To: linux-kernel@...r.kernel.org Subject: ioctl's suck? The other day Linus (I think) made the statement, that I don't disagree with, that I will parapharse as "ioctl's suck". If I recall correctly and understand he was saying that a device that uses ioctls is broken. (this is my paraphrase and if it offends anybody it is my fault not the original author's). This got me to thinking about a device driver that I'm working on. Currently I have some ioctls to handle status and out of band messages and I'm wondering about eliminating the ioctls. I'm wondering if anybody has any ideas or opinions that they would like to share, about just what i wrong with ioctls and/or how to avoid them. I can see a number of problems with ioctls that I can'tr quite put into words. I could add a control device and pass ascii strings for status and OOB messages, would that be an improvement? -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting a bad thing? Brian Beattie LFS12947 | "Honor isn't about making the right choices. beattie@...ttie-home.net | It's about dealing with the consequences." www.beattie-home.net | -- Midori Koto -- 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