[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161014150437.GY19318@brightrain.aerifal.cx>
Date: Fri, 14 Oct 2016 11:04:37 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: [PATCH 1/7] fix preadv2 and pwritev2 syscall numbers on
x32 for linux v4.8
On Fri, Oct 14, 2016 at 02:09:10PM +0200, Khem Raj wrote:
> On Sun, Oct 9, 2016 at 6:58 PM, Szabolcs Nagy <nsz@...t70.net> wrote:
> > the numbers were wrong in musl, but they were also wrong in the kernel
> > and got fixed in v4.8 commit 3ebfd81f7fb3e81a754e37283b7f38c62244641a
>
> what happens if we now build musl trunk with linux kernel 3.7 ?
There's no such thing as "building musl with linux 3.7". musl need not
be built on a Linux system at all; there's no build-time dependency on
Linux, only run-time.
As for what happens at run-time, the wrong values of the syscall
numbers presumably don't work at all, or worse yet do the wrong thing.
I'm not sure if the fixed values work if called when running on the
old kernel, but for practical purposes that kernel should just be
considered buggy/not-usable or "not supporting these new syscalls
yet" for x32. In any case they're new nonstandard ones and essentially
unused at this time.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
