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: <46EF90A3.2050109@linux-kernel.at>
Date:	Tue, 18 Sep 2007 10:47:31 +0200
From:	Oliver Falk <oliver@...ux-kernel.at>
To:	Adrian Bunk <bunk@...nel.org>
CC:	linux-kernel@...r.kernel.org, axp-list@...hat.com,
	Jay Estabrook <jay.estabrook@...com>,
	ac-admin@...ts.anotherbloody.com
Subject: Re: 2.6.23 alpha unistd.h changes

On 09/17/2007 11:41 PM, Adrian Bunk wrote:
> On Mon, Sep 17, 2007 at 10:33:07PM +0200, Oliver Falk wrote:
>> Hi!
> 
> Hi Oliver!
> 
>> ...
>> As these additions are quite new to upstream kernel, but at Alphacore we
>> have patched it since a while now (I don't know about other Alpha ports;
>> Debian folks may speak up now!), I would suggest to use the same
>> 'ordering' of the syscalls upstream and add the new syscalls that we had
>> not in place, but are now upstream to the end of our 'old' list.
>> ...
> 
> I just checked:
> 
> It seems Debian didn't patch them into the kernel at all, and since two 
> months Debian unstable ships kernel 2.6.22 with the upstream syscall 
> numbers.

That's possible a problem. Right. Someone with contacts to Debian here?
If Debian hasn't rebuilt glibc against the new headers, we could change
it without problems.

If not, we have a problem on AC... Anyone with a glibc that was compiled
against our patched unistd.h (so including the new syscall numbers),
will not be able to upgrade the kernel, but also needs to upgrade glibc
and then *must* reboot :-(

Best,
 Oliver
-
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/