From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Roland McGrath" <roland@redhat.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"kernel list" <linux-kernel@vger.kernel.org>,
"Ulrich Drepper" <drepper@redhat.com>,
"Vegard Nossum" <vegard.nossum@gmail.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: [PATCH] sys_waitid: return -EFAULT for NULL
Date: Wed, 14 Jan 2009 13:53:10 +1300 [thread overview]
Message-ID: <cfd18e0f0901131653y76a827b5i906fadce63ada56b@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0901131629220.6528@localhost.localdomain>
On Wed, Jan 14, 2009 at 1:33 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Tue, 13 Jan 2009, Roland McGrath wrote:
>>
>> It's always been invalid to call waitid() with a NULL pointer. It was an
>> oversight that it was allowed (and acts like a wait4() call instead).
>
> I'm not going to take this.
>
> If it was some new system call, of if there was some downside to out
> behavior, I might be interested. As it is, our behaviour has zero
> downside, and changing existing interfaces simply isn't worth it.
It has zero downside for *us*. But it is yet another example of Linux
littering the Unix landscape with unnecessary inconsistencies that
application writers must deal with. That's a downside for the app
writers. (But, given how long the existing behavior has been in the
wild, my argument here is somewhat academic...)
> The alleged "downsides" are bogus:
>
> - POSIX is not that strict.
Well, POSIX.1-2001 is fairly clear:
The application shall ensure that the infop argument points to
a siginfo_t structure.
(Admittedly, this is a requirement imposed on the application, rather
than the implementation, but the standard goes on to say that the
implemenation shall fill in the structure pointed to by infop.)
Cheers,
Michael
> EFAULT is one of the odd error cases anyway,
> and even explicit requirements are irrelevant: if somebody wants to get
> strict conformance paperwork done, you just need to tell where you
> differ, and you're basically done. But perhaps more important, nobody
> cares.
>
> - The "portability" argument is totally bogus, since it's not like you
> compile programs without even testing to another UNIX _anyway_.
>
> So I'm simply not going to potentially break binaries over something that
> is so _totally_ irrelevant. Document it in the man-page instead.
Well, that's doable of course.
--
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
next prev parent reply other threads:[~2009-01-14 0:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cfd18e0f0901131436ud2cf61bkf0e6b00f4b765bb5@mail.gmail.com>
2009-01-13 22:38 ` waitid() return value strangeness when infop is NULL Michael Kerrisk
2009-01-13 22:43 ` Michael Kerrisk
2009-01-13 22:47 ` Roland McGrath
2009-01-13 22:49 ` [PATCH] sys_waitid: return -EFAULT for NULL Roland McGrath
2009-01-13 23:14 ` Michael Kerrisk
2009-01-13 23:24 ` Andrew Morton
2009-01-13 23:36 ` Michael Kerrisk
2009-01-13 23:47 ` Roland McGrath
2009-01-14 0:13 ` Michael Kerrisk
2009-01-14 0:24 ` Ulrich Drepper
2009-01-14 0:33 ` Linus Torvalds
2009-01-14 0:53 ` Michael Kerrisk [this message]
2009-01-14 0:57 ` Linus Torvalds
2009-01-14 1:39 ` Michael Kerrisk
2009-01-14 2:10 ` Linus Torvalds
2009-01-14 2:28 ` Michael Kerrisk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfd18e0f0901131653y76a827b5i906fadce63ada56b@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®