linux-kernel - Re: [PATCH 3/4] DRBG: Fix format string for debugging statements

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

Date:	Sat, 05 Jul 2014 02:27:27 +0200
From:	Stephan Mueller <smueller@...onox.de>
To:	Joe Perches <joe@...ches.com>
Cc:	Dan Carpenter <dan.carpenter@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	kbuild test robot <fengguang.wu@...el.com>, kbuild@...org,
	linux-crypto@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/4] DRBG: Fix format string for debugging statements

Am Freitag, 4. Juli 2014, 17:24:09 schrieb Joe Perches:

Hi Joe,

> On Sat, 2014-07-05 at 02:15 +0200, Stephan Mueller wrote:
> > Am Freitag, 4. Juli 2014, 17:09:33 schrieb Joe Perches:
> > > On Sat, 2014-07-05 at 01:57 +0200, Stephan Mueller wrote:
> > > > And I also get the same output. Yet I am not sure how that code can be
> > > > compared to the code in the kernel.
> > > 
> > > What that code shows is that the ARRAY_SIZE
> > > type is size_t.
> > > 
> > > The difference is ARRAY_SIZE in the kernel
> > > should be output with %zu.
> > 
> > Using %zu works without a warning on my 64 bit machine. So you are saying
> > that ARRAY_SIZE will always be size_t on every architecture? If yes, I
> > will update my patch.
> 
> Hi again.
> 
> ARRAY_SIZE is size_t in all architectures.

Thank you very much, this is the answer I was looking for :-)

I will update the patch accordingly.

-- 
Ciao
Stephan
--
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/