linux-kernel - Re: [PATCH v2] 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: <200901021547.32666.vapier@gentoo.org>
Date:	Fri, 2 Jan 2009 15:47:30 -0500
From:	Mike Frysinger <vapier@...too.org>
To:	Andreas Schwab <schwab@...e.de>
Cc:	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
	David Woodhouse <dwmw2@...radead.org>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Patrick McHardy <kaber@...sh.net>,
	"David S. Miller" <davem@...emloft.net>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2] linux/types.h: always export 64bit aligned defines

On Friday 02 January 2009 09:24:39 Andreas Schwab wrote:
> Mike Frysinger <vapier@...too.org> writes:
> > These these defines dont actually conflict with normal userspace / C
> > library types, there's no reason to hide them behind the
> > __KERNEL_STRICT_NAMES define.
>
> aligned_u64 would pollute the name space, wouldn't it?

if by "pollute the name space" you mean "it'll be defined where it normally 
wasnt before", then yes.  it's always been in the header, just behind 
__KERNEL_STRICT_NAMES.  i also highlight the fact that existing headers that 
are exported to userspace are already using this type, so they're broken most 
of the time today.

unless you want a completely new patch that deletes aligned_*64 types and 
replaces them with __aligned_*64 types ...
-mike

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