From: Benjamin LaHaise <bcrl@redhat.com>
To: Keith Owens <kaos@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Assigning syscall numbers for testing
Date: Sat, 22 Dec 2001 18:25:57 -0500 [thread overview]
Message-ID: <20011222182556.A19700@redhat.com> (raw)
In-Reply-To: <20011222140126.B19442@redhat.com> <17322.1009063106@ocs3.intra.ocs.com.au>
In-Reply-To: <17322.1009063106@ocs3.intra.ocs.com.au>; from kaos@sgi.com on Sun, Dec 23, 2001 at 10:18:26AM +1100
On Sun, Dec 23, 2001 at 10:18:26AM +1100, Keith Owens wrote:
> You did not read my mail all the way through, did you? I said -
>
> If the [user space] code cannot open /proc/dynamic_syscalls or cannot
> find the desired syscall name, fall back to the assigned syscall number
> (if any) or fail if there is no assigned syscall number. By falling
> back to the assigned syscall number, new versions of the user space
> code are backwards compatible, on older kernels it will use the dynamic
> syscall number, on newer kernels it will use the assigned number.
No, that's not the case I'm talking about: what happens when a vendor
starts shipping this patch and Linus decides to add a new syscall that
uses a syscall number that the old kernel used for dynamic syscalls?
-ben
--
Fish.
next prev parent reply other threads:[~2001-12-22 23:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-22 11:28 [patch] Assigning syscall numbers for testing Keith Owens
2001-12-22 14:12 ` Alan Cox
2001-12-22 14:32 ` Keith Owens
2001-12-22 19:01 ` Benjamin LaHaise
2001-12-22 23:18 ` Keith Owens
2001-12-22 23:25 ` Benjamin LaHaise [this message]
2001-12-23 0:02 ` Keith Owens
2001-12-23 4:04 ` Chris Vandomelen
2001-12-23 5:10 ` Keith Owens
2001-12-23 17:06 ` Benjamin LaHaise
2001-12-23 19:15 ` Davide Libenzi
2001-12-24 1:01 ` Keith Owens
2001-12-24 16:52 ` Doug Ledford
2001-12-24 17:11 ` Alan Cox
2001-12-24 17:06 ` Doug Ledford
2001-12-24 17:34 ` David Lang
2001-12-24 18:13 ` Doug Ledford
2001-12-24 17:54 ` David Lang
2001-12-24 18:23 ` Doug Ledford
2001-12-26 16:22 ` Riley Williams
2001-12-25 2:18 ` Keith Owens
2001-12-25 10:00 ` Russell King
2001-12-24 18:23 ` Alan Cox
2001-12-24 18:16 ` Doug Ledford
2001-12-24 19:05 ` Alan Cox
2001-12-24 19:31 ` Russell King
2001-12-24 20:46 ` Alan Cox
2001-12-24 23:28 ` Edgar Toernig
2001-12-24 23:43 ` Andreas Steinmetz
2001-12-22 20:51 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2001-12-22 11:35 Keith Owens
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=20011222182556.A19700@redhat.com \
--to=bcrl@redhat.com \
--cc=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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