netdev - Re: Kernel header changes break glibc build

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]

Date:	Wed, 6 Dec 2006 15:18:41 +0100
From:	Jakub Jelinek <jakub@...hat.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Thomas Graf <tgraf@...g.ch>, Ulrich Drepper <drepper@...hat.com>,
	"Joseph S. Myers" <joseph@...esourcery.com>,
	netdev@...r.kernel.org, libc-alpha@...rceware.org, akpm@...l.org,
	"David S. Miller" <davem@...emloft.net>
Subject: Re: Kernel header changes break glibc build

On Wed, Dec 06, 2006 at 02:07:19PM +0000, David Woodhouse wrote:
> On Wed, 2006-12-06 at 14:59 +0100, Thomas Graf wrote:
> > Are you suggesting that the kernel has to keep macros around which
> > are of no use to the kernel itself just because glibc uses them?
> 
> No, although in fact that _is_ the only reason we use these horrid __uXX
> types rather than proper C datatypes, isn't it?

There are the kernel's own headers and kernel ABI headers for userland use.
Until recently the latter has been maintained by various distributions
and manually occassionally updated to sync a little bit with kernel ABI
additions (new syscalls, etc.)., but now, thanks to David, these are
generated from kernel's own headers.  If the macros were part of
such ABI (I don't think these macros were meant to be #ifdef __KERNEL__
and just by omission exported to userland), then if you change
the kernel headers (which of course you can do, that's kernel private
headers), then you IMNSHO should also add magic to make headers_install
to keep the kernel ABI headers for userland headers stable.
Which in this case would mean if you decide rtnetlink.h shouldn't include
the newly added if_addr.h that you add rules for generating the userland
rtnetlink.h such that it will include linux/if_addr.h and define the
macros you intentionally omitted.

	Jakub
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html