Messages in this thread | | | Date | Tue, 30 Nov 2004 15:46:49 +0000 | From | Al Viro <> | Subject | Re: Problem with ioctl command TCGETS |
| |
On Tue, Nov 30, 2004 at 02:26:19PM +0100, Pavel Machek wrote: > > Think read(2)/write(2). We already have several barfbags too many, > > and that includes both ioctl() and setsockopt(). We are stuck with > > them for compatibility reasons, but why the hell would we need yet > > another one? > > Passing structure using read/write is evil, because there's nowhere to hook > 32/64 bit translation.
No, really? And we must use different layouts for 32 and 64 bit platforms for which religious reasons, exactly? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |