linux-kernel - Re: [PATCH 01/24] types: create <asm-generic/int-*.h>

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]

Date:	Fri, 25 Apr 2008 13:28:58 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Arch Mailing List <linux-arch@...r.kernel.org>
Subject: Re: [PATCH 01/24] types: create <asm-generic/int-*.h>

On Fri, Apr 25, 2008 at 12:10:40PM -0700, H. Peter Anvin wrote:
> Well, compatibility with userspace is probably one aspect of that. 
> x86-64 is the odd man out there, it defines __s64 as "long long" even 
> for userspace, even though int64_t from <stdint.h> is "long".  This, 
> IMO, is the Wrong Thing, but it's a separate set of changes.
> 
> The right thing to do is probably to always use "long long" in the 
> kernel, while defining __s64 et al as "long" on 64-bit platforms when 
> not under __KERNEL__.
> 
> Again, this is a separate set of changes from this patchset, which is 
> just a code transformation.

Understood, and agreed.  It just seemed like an opportune time to
mention the problem of printing a u64.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."
--
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/