From: Arjan van de Ven <arjan@infradead.org>
To: Michael Kerrisk <michael.kerrisk@gmx.net>
Cc: Ulrich Drepper <drepper@redhat.com>,
manfred@colorfullife.com, linux-kernel@vger.kernel.org,
tytso@mit.edu, torvalds@osdl.org, eggert@cs.ucla.edu,
roland@redhat.com, rlove@rlove.org, mtk-lkml@gmx.net,
mtk-manpages@gmx.net
Subject: Re: Strange Linux behaviour with blocking syscalls and stop signals+SIGCONT
Date: Fri, 07 Jul 2006 09:20:56 +0200 [thread overview]
Message-ID: <1152256856.3111.20.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060707070334.186790@gmx.net>
> There must be some framework for changing the kernel ABI over time.
> We can't remain forever stuck with an ABI behaviour because
> of the development model (i.e., no 2.7/2.8).
Hi,
this has nothing to do with the development model. The userspace syscall
ABI *has* to be stable. If we make a mistake that's a high price but we
pay it. This fwiw is one of the reasons we are/should be very careful
with adding system calls, and make sure the behavior is indeed right.
It's also the reason we're not so happy about new ioctls; they're
effectively mini-system calls with the same ABI issues, but just less
controlled/reviewed/designed/visible.
Greetings,
Arjan van de Ven
next prev parent reply other threads:[~2006-07-07 7:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 14:46 Michael Kerrisk
2006-07-04 19:02 ` Manfred Spraul
2006-07-06 9:23 ` Michael Kerrisk
2006-07-06 18:42 ` Manfred Spraul
2006-07-06 18:55 ` Ulrich Drepper
2006-07-06 19:02 ` Manfred Spraul
2006-07-06 19:10 ` Ulrich Drepper
2006-07-06 19:18 ` Linus Torvalds
2006-07-06 19:28 ` Manfred Spraul
2006-07-06 19:29 ` Manfred Spraul
2006-07-07 4:57 ` Michael Kerrisk
2006-07-07 5:10 ` Linus Torvalds
2006-07-07 5:12 ` Linus Torvalds
2009-11-07 19:43 ` angelo.borsotti
2006-07-07 4:32 ` Michael Kerrisk
2006-07-07 4:57 ` Ulrich Drepper
2006-07-07 5:07 ` Michael Kerrisk
2006-07-07 6:20 ` Ulrich Drepper
2006-07-07 7:03 ` Michael Kerrisk
2006-07-07 7:20 ` Arjan van de Ven [this message]
2006-07-07 8:02 ` Michael Kerrisk
2006-07-07 9:26 ` Jakub Jelinek
2006-07-07 13:36 ` Ulrich Drepper
2006-07-07 4: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=1152256856.3111.20.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=drepper@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-lkml@gmx.net \
--cc=mtk-manpages@gmx.net \
--cc=rlove@rlove.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.org \
--cc=tytso@mit.edu \
/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®