From: Arjan van de Ven <arjan@infradead.org>
To: Chris Wedgwood <cw@f00f.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Andrew Morton <akpm@osdl.org>,
matthias@corelatus.se, linux-kernel@vger.kernel.org
Subject: Re: patch to fix set_itimer() behaviour in boundary cases
Date: Sat, 15 Jan 2005 21:20:59 +0100 [thread overview]
Message-ID: <1105820460.6300.86.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050115195504.GA10754@taniwha.stupidest.org>
On Sat, 2005-01-15 at 11:55 -0800, Chris Wedgwood wrote:
> On Sat, Jan 15, 2005 at 10:58:45AM +0100, Arjan van de Ven wrote:
>
> > I don't see a valid reason to restrict/reject input that is accepted
> > now and dealt with reasonably because some standard says so (if you
> > design a new api, following the standard is nice of course). I don't
> > see "doesn't reject a condition that can reasonable be dealt with"
> > as a good reason to go double ABI at all.
>
> we could printk for now and if nobody reports this to lkml (as they
> do/did with oldish tcpdump/libpcap a while ago) we could -EINVAL
>
but why????
if someone wants the stuff rejected in a posix confirm way, he can do
these tests easily in the syscall wrapper he needs anyway for this
function.
next prev parent reply other threads:[~2005-01-15 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 8:45 Matthias Lang
2005-01-15 9:30 ` Andrew Morton
2005-01-15 9:36 ` William Lee Irwin III
2005-01-15 9:58 ` Arjan van de Ven
2005-01-15 10:07 ` William Lee Irwin III
2005-01-15 19:55 ` Chris Wedgwood
2005-01-15 20:20 ` Arjan van de Ven [this message]
2005-01-15 23:25 ` Matthias Lang
2005-01-15 23:39 ` Randy.Dunlap
2005-01-16 0:58 ` Alan Cox
2005-01-16 12:11 ` Arjan van de Ven
2005-01-19 23:51 ` George Anzinger
2005-01-20 8:07 ` Arjan van de Ven
2005-01-20 23:12 ` George Anzinger
2005-01-21 7:49 ` Arjan van de Ven
2005-01-21 8:22 ` George Anzinger
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=1105820460.6300.86.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.org \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias@corelatus.se \
--cc=wli@holomorphy.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®