linux-kernel - Re: [PATCH] linux/types.h: always export 64bit aligned defines

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: <200801291916.21133.vapier@gentoo.org>
Date:	Tue, 29 Jan 2008 19:16:20 -0500
From:	Mike Frysinger <vapier@...too.org>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Sam Ravnborg <sam@...nborg.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH] linux/types.h: always export 64bit aligned defines

On Tuesday 29 January 2008, Jan Engelhardt wrote:
> On Jan 27 2008 21:33, Andrew Morton wrote:
> >On Sat, 26 Jan 2008 04:23:21 -0500 Mike Frysinger <vapier@...too.org> 
wrote:
> >> Some kernel headers exported to userspace rely on these 64bit
> >> aligned defines. However, they are hidden behind
> >> __KERNEL_STRICT_NAMES at the moment which means most of the time,
> >> they're never actually available.
>
> Wrong way.

i'm thinking the right way, i just may not have expressed it completely 
clearly ...

> They are inside #ifndef __KERNEL_STRICT_NAMES, so 
> they _are_ available to userspace.

for all practical purposes, they are not.  glibc will define 
__KERNEL_STRICT_NAMES because (like a sane C lib), it defines all of the 
basic types that the kernel also defines.
-mike

Download attachment "signature.asc " of type "application/pgp-signature" (828 bytes)