This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] <bits/syscall.h>: Use an arch-independent system call list on Linux


On Apr 06 2017, Florian Weimer <fweimer@redhat.com> wrote:

> On 04/06/2017 10:00 AM, Andreas Schwab wrote:
>> On Apr 05 2017, Florian Weimer <fweimer@redhat.com> wrote:
>>
>>> Downstream, we have the problem that we need to deliver our glibc packages
>>> before the kernel team finishes backporting system calls.  This means that
>>> the final glibc build before a release does not contain all the SYS_*
>>> macros supported by the kernel headers.
>>
>> Why can't you just patch the kernel headers package?
>
> Wasn't this rejected on this list because that would lead to a namespace
> violation?

I don't understand.  The kernel uapi headers fully respect namespace,
at least those used by glibc.

> The system call list is generated in an architecture-specific manner.

Sure, but the commits that add the syscalls are easily separable.  All
you need is to update the files underneath asm/unistd.h, which are
pretty regular.

> I looked into this, most architectures use some construct which is
> rather impenetrable.  It's also very brittle in the sense that you can
> easily change the userspace ABI by accident, and nothing in the kernel
> build will tell you that you just did.

You only need to patch the kernel headers package, which is hopefully
separate from the kernel.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]