linux-kernel - Re: 2.6.23 alpha unistd.h changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46EF922A.4030206@linux-kernel.at>
Date:	Tue, 18 Sep 2007 10:54:02 +0200
From:	Oliver Falk <oliver@...ux-kernel.at>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Richard Henderson <rth@...ddle.net>, linux-kernel@...r.kernel.org,
	axp-list@...hat.com, Jay Estabrook <jay.estabrook@...com>,
	ac-admin@...ts.anotherbloody.com, ink@...assic.park.msu.ru
Subject: Re: 2.6.23 alpha unistd.h changes

On 09/17/2007 11:22 PM, Adrian Bunk wrote:
> On Mon, Sep 17, 2007 at 10:33:07PM +0200, Oliver Falk wrote:
>> At Alphacore we used to patch the kernel headers for a while now; We
>> added syscalls __NR_openat (447) until __NR_tee (466).
> 
> Why did your numbers differ from the numbers that were used in the 
> upstream kernel?

Afaik, our patch was done a while ago and nobody every submitted it
upstream - don't know why...

At AC, we follow RH/Fedora packages and there we had glibc-kernheaders -
where our patch originates. When the glibc/kernel packages changed and
glibc-kernheaders died, I patched the syscalls into kernel headers; Not
thinking that I better submit it upstream. :-(

> The Alpha maintainers (Cc's added) might now better what happened here.
> 
>> However, since 2.6.23 these syscall where added upstream, but with
>> different syscall numbers; What happens is the following:
>> ...
> 
> These syscalls were added in 2.6.22, not 2.6.23, and are therefore in 
> the officially released kernel since more than two months.

Yes, 2.6.22, I've just encountered the problem with 2.6.23...

> Changing a userspace ABI that has already been part of an officially 
> released kernel because someone patched other syscall numbers into his 
> private kernel doesn't sound like a good solution.

As I wrote in my previous mail, that's true, but if Debian folks haven't
recompiled glibc against the new headers we can change it without
breaking something...

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