linux-kernel - Re: [PATCH 6/7] remove all remaining

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] [day] [month] [year] [list]

Date:	Wed, 30 Aug 2006 19:45:47 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Andi Kleen <ak@...e.de>
Cc:	Arnd Bergmann <arnd@...db.de>,
	David Woodhouse <dwmw2@...radead.org>,
	David Miller <davem@...emloft.net>, linux-arch@...r.kernel.org,
	jdike@...toit.com, B.Steinbrink@....de, arjan@...radead.org,
	chase.venters@...entec.com, akpm@...l.org,
	rmk+lkml@....linux.org.uk, rusty@...tcorp.com.au,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6/7] remove all remaining _syscallX macros

On Mon, Aug 28, 2006 at 07:00:09PM +0200, Andi Kleen wrote:
> 
> > This would only be required if you'd upgrade the userspace kernel
> > headers on this system to a version not matching the ones glibc was
> > built against - and this has never been considered a good idea
> > (it should work in theory, but not with our current header mess).
> 
> Sorry, but that's just utterly wrong. It has always worked. The kernel ABI
> is stable on this level.

In this area, the ABI is much more stable than the API.

Try compiling glibc-2.0.1 with 2.6.17 kernel headers...

> -Andi

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/