linux-kernel - Re: trace: fix printk warning for u64

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:	Mon, 27 Oct 2008 22:06:55 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Ingo Molnar <mingo@...e.hu>, Linus <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: trace: fix printk warning for u64

On Tue, 28 Oct 2008 00:12:54 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Ingo,
> 
> On Mon, 27 Oct 2008 10:52:48 +0100 Ingo Molnar <mingo@...e.hu> wrote:
> >
> > (btw., did the "unify u64 definitions across all platforms" project 
> > get anywhere?)
> 
> I think (from a comment from DaveM) that it led into a real mess.

The problem is the large amount of arch-specific code which is printing
u64's with %lu because it "knows" that u64 is implemented as ulong. 
They all need to be switched to %ll.

A better strategy to get all this done would be to convert the
offending architectures to `long long' individually.  Then when that's
all done, unifying the typedef is a trivial 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/