linux-kernel - Re: linux-next: Tree for October 21 (printk format warnings)

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] [day] [month] [year] [list]

Message-Id: <20081021.222020.05274832.davem@davemloft.net>
Date:	Tue, 21 Oct 2008 22:20:20 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	randy.dunlap@...cle.com
Cc:	greg@...ah.com, sfr@...b.auug.org.au, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: Tree for October 21 (printk format warnings)

From: Randy Dunlap <randy.dunlap@...cle.com>
Date: Tue, 21 Oct 2008 22:11:16 -0700

> On Tue, 21 Oct 2008 22:07:54 -0700 (PDT) David Miller wrote:
> 
> > From: Greg KH <greg@...ah.com>
> > Date: Tue, 21 Oct 2008 22:01:42 -0700
> > 
> > > What's the expected modifier for "size_t" to work on all arches?
> > 
> > Put "%Z" in front of the output specifier you want to use,
> > for example %Zd for decimal and %Zx for hex.
> > 
> > > Same goes for the result of "size_of()", what should we use there?  Or
> > > are we just required to always cast things?
> > 
> > Sizeof should use the same as above.
> 
> I know that Alan recently merged a patch with %Zd instead of %zd,
> but the ANSI spec says to use %z, so I thought that we were going with
> that moreso than %Z... ??

I think you're right.

My old fingers must do %Z automatically because gcc a long time ago
didn't recognize %z and warned.  That should be such an old gcc problem
as to be irrelevant these days.
--
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/