linux-kernel - asm-x86/* exported headers using CONFIG_X86

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

Message-Id: <200710160054.00138.arnd@arndb.de>
Date:	Tue, 16 Oct 2007 00:53:58 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	linux-kernel@...r.kernel.org
Cc:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: asm-x86/* exported headers using CONFIG_X86_32

While looking through the new header files, I noticed lots of occurences
of #ifdef CONFIG_X86_32 in headers files exported for glibc.

This is fundamentally broken because user applications including them
do not know about any CONFIG_* symbols, and if they did, those
would incorrectly describe the ABI.

I guess in most cases, the headers that are interesting to user space
can simply be merged without any such #ifdef remaining, but those
that are still needed should be converted to use #ifdef __x86_64__,
which is set by the compiler.
This is how the other architectures avoid this particular problem.

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