linux-kernel - x86: <asm/sigcontext.h> not exported, but <asm/sigcontext32.h> is?

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

Message-ID: <472AA22C.20306@zytor.com>
Date:	Thu, 01 Nov 2007 21:06:04 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	David Woodhouse <dwmw2@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@...e.de>
Subject: x86: <asm/sigcontext.h> not exported, but <asm/sigcontext32.h> is?

Anyone happens to know how come, in the x86 tree (and previously in the 
x86-64 tree), <asm/sigcontext.h> is not exported to userspace (but uses 
userspace-compatible typenames), whereas <asm/sigcontext32.h> is?

This is particularly puzzling since at least my version of glibc 
contains an <asm/sigcontext.h> that looks just like the one in the 
kernel, minus a __user and an inclusion of <linux/compiler.h>.

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