linux-kernel - Re: How do I printk <type> correctly?

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: <1224837703.6002.86.camel@johannes.berg>
Date:	Fri, 24 Oct 2008 10:41:43 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	David Miller <davem@...emloft.net>
Cc:	adobriyan@...il.com, linux-kernel@...r.kernel.org
Subject: Re: How do I printk <type> correctly?

On Thu, 2008-10-23 at 13:40 -0700, David Miller wrote:

> > An "unsigned long long" is 64-bits too even on 64-bit platforms, so
> > why the difference? Are there any differences like alignment on some
> > platforms?
> 
> I invite you to go make that change and then try to fixup all the
> resulting build warnings.  Some of us already made an attempt at
> some point in the past. :-/

Heh, ok. I was just curious really. I think that answers it well
enough :)

> But it's just papering over the core problem, that we can't extend
> gcc's automatic printf format type checking easily.
> 
> Even if we make u64 the same type everywhere, things like sector_t
> and other types which do have to vary by architecture will need
> to be casted.

Indeed, it doesn't really help that much.

johannes

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