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, 14 Jan 2009 15:28:35 +1300 From: "Michael Kerrisk" <mtk.manpages@...glemail.com> To: "Linus Torvalds" <torvalds@...ux-foundation.org> Cc: "Roland McGrath" <roland@...hat.com>, "Andrew Morton" <akpm@...ux-foundation.org>, "kernel list" <linux-kernel@...r.kernel.org>, "Ulrich Drepper" <drepper@...hat.com>, "Vegard Nossum" <vegard.nossum@...il.com>, "linux-man@...r.kernel.org" <linux-man@...r.kernel.org> Subject: Re: [PATCH] sys_waitid: return -EFAULT for NULL On Wed, Jan 14, 2009 at 3:10 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > > On Wed, 14 Jan 2009, Michael Kerrisk wrote: >> >> It isn't an extension. It's an accident. > > Bah. It doesn't matter. It's an ABI. Your arguments make no sense - simply > because there are other differences that means that if you develop under > one OS, you can't expect it to run on another. (I don't think implied such an expectation. On the other hand, we can do things to make more or less difficult for writers of portable applications.) > Arguing that "accident" is somehow different than "extension" is a totally > inane and _idiotic_ argument. Because it's just arguing about the words, > not about the end result. > > If you're doing a dissertation in English literature, arguing about the > words you use is valid. But if you're talking about operating systems, > it's just pointless masturbation. I agree that for practical purposes with respect to waitid(), "extension" versus "accident" is only about words: we've had the interface in its current form for so long that changing it shouldn't be done without consideration. But (and this was why I constrasted "extension" with "accident"), I already made it clear that IMO there was another point that was more important than this specific case: : And the fact that such accidents happen more often than necessary is : the real problem, rather than the fact that this API in particular is : inconsistent with expectations. but you responded to the point I found less important. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html -- 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