From: Keith Owens <kaos@sgi.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Assigning syscall numbers for testing 
In-Reply-To: Your message of "Sat, 22 Dec 2001 14:01:26 CDT."
             <20011222140126.B19442@redhat.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 23 Dec 2001 10:18:26 +1100
Message-ID: <17322.1009063106@ocs3.intra.ocs.com.au>
Sender: linux-kernel-owner@vger.kernel.org

On Sat, 22 Dec 2001 14:01:26 -0500, 
Benjamin LaHaise <bcrl@redhat.com> wrote:
>On Sat, Dec 22, 2001 at 10:28:55PM +1100, Keith Owens wrote:
>> The patch below dynamically assigns a syscall number to a name and
>> exports the number and name via /proc.  Dynamic assignment removes the
>> collision problem.  Exporting via /proc allows user space code to
>> automatically find out what the syscall number is this week.  strace
>> could read the /proc output to print the syscall name, although it
>> still cannot print the arguments.
>
>Doesn't work.  You've still got problems running binaries compiled against 
>newer kernels (say, glibc supporting a new syscall) against the dynamic 
>syscall.  Numbers don't work, plain and simple.

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/