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: <jer63lfjy0.fsf@sykes.suse.de>
Date:	Fri, 02 Jan 2009 22:59:35 +0100
From:	Andreas Schwab <schwab@...e.de>
To:	Mike Frysinger <vapier@...too.org>
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

Mike Frysinger <vapier@...too.org> writes:

> 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.

I mean that it may conflict with normal userspace which is the whole
point of being hidden.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@...e.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
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/