From: Stephan Mueller <smueller@chronox.de>
To: Joe Perches <joe@perches.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Herbert Xu <herbert@gondor.apana.org.au>,
kbuild test robot <fengguang.wu@intel.com>,
kbuild@01.org, linux-crypto@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] DRBG: Fix format string for debugging statements
Date: Sat, 05 Jul 2014 01:57:50 +0200 [thread overview]
Message-ID: <3856718.HehN4Xqlpl@myon.chronox.de> (raw)
In-Reply-To: <1404493040.6384.21.camel@joe-AO725>
Am Freitag, 4. Juli 2014, 09:57:20 schrieb Joe Perches:
Hi Joe,
> On Fri, 2014-07-04 at 14:21 +0300, Dan Carpenter wrote:
> > On Sat, Jun 28, 2014 at 08:53:19PM -0700, Joe Perches wrote:
> > > On Sun, 2014-06-29 at 05:46 +0200, Stephan Mueller wrote:
> > > > Am Sonntag, 29. Juni 2014, 12:24:02 schrieb Stephen Rothwell:
> > > >
> > > > Hi Stephen,
> > > >
> > > > > Hi Stephan,
> > > > >
> > > > > On Sat, 28 Jun 2014 22:01:46 +0200 Stephan Mueller
> > > > > <smueller@chronox.de>
> > > >
> > > > wrote:
> > > > > > @@ -1987,8 +1987,9 @@ static int __init drbg_init(void)
> > > > > >
> > > > > > if (ARRAY_SIZE(drbg_cores) * 2 > ARRAY_SIZE(drbg_algs)) {
> > > > > >
> > > > > > pr_info("DRBG: Cannot register all DRBG types"
> > > > > >
> > > > > > - "(slots needed: %lu, slots available: %lu)\n",
> > > > > > - ARRAY_SIZE(drbg_cores) * 2,
ARRAY_SIZE(drbg_algs));
> > > > > > + "(slots needed: %u, slots available: %u)\n",
> > > > > > + (unsigned int)ARRAY_SIZE(drbg_cores) * 2,
> > > > > > + (unsigned int)ARRAY_SIZE(drbg_algs));
> > > > >
> > > > > Doesn't ARRAY_SIZE() always return a size_t? In which case surely
> > > > > we
> > > > > need no casts, but need to us %zu in the format string.
> > > >
> > > > Unfortunately not at all. On my x86_64, I get the compiler warning
> > > > that
> > > > ARRAY_SIZE is a long unsigned int without the cast.
>
> It doesn't seem to for 4.8.
> Is there some specific gcc version where this occurs?
$ LANG=en_US gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.3/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --
infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --
enable-bootstrap --enable-shared --enable-threads=posix --enable-
checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-
exceptions --enable-gnu-unique-object --enable-linker-build-id --with-linker-
hash-style=gnu --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto
--enable-plugin --enable-initfini-array --enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-
multifile --enable-java-maintainer-mode --with-ecj-
jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-
isl=/builddir/build/BUILD/gcc-4.8.3-20140624/obj-x86_64-redhat-linux/isl-
install --with-cloog=/builddir/build/BUILD/gcc-4.8.3-20140624/obj-x86_64-
redhat-linux/cloog-install --with-tune=generic --with-arch_32=i686 --
build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.3 20140624 (Red Hat 4.8.3-1) (GCC)
Note, I get a warning when compiling 64 bit with %u and without the unsigned
int cast. Initially I had %lu without the cast which worked on my x86_64, but
it was reported that this usage caused a warning on 32 bit. So, there is a
different type of ARRAY_SIZE.
> I get the same output types and error warnings compiling this
> either -m32 or -m64
I do not get a warning for the ARRAY_SIZE thing with your code with either -
m32 or -m64 (I get other warnings though, which should not be of interest
here).
And I also get the same output. Yet I am not sure how that code can be
compared to the code in the kernel.
--
Ciao
Stephan
next prev parent reply other threads:[~2014-07-04 23:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 19:57 [PATCH 0/4] DRBG: Fixes for sparse tool reports Stephan Mueller
2014-06-28 19:58 ` [PATCH 1/4] DRBG: use of kernel linked list Stephan Mueller
2014-07-04 14:11 ` Herbert Xu
2014-06-28 20:00 ` [PATCH 2/4] DRBG: cleanup of preprocessor macros Stephan Mueller
2014-06-29 2:20 ` Stephen Rothwell
2014-06-29 5:07 ` Stephan Mueller
2014-06-29 7:41 ` Randy Dunlap
2014-06-29 11:37 ` Stephan Mueller
2014-07-04 14:15 ` Herbert Xu
2014-07-05 0:03 ` Stephan Mueller
2014-06-28 20:01 ` [PATCH 3/4] DRBG: Fix format string for debugging statements Stephan Mueller
2014-06-29 2:24 ` Stephen Rothwell
2014-06-29 3:46 ` Stephan Mueller
2014-06-29 3:53 ` Joe Perches
2014-06-29 4:54 ` Stephan Mueller
2014-07-04 11:21 ` Dan Carpenter
2014-07-04 16:57 ` Joe Perches
2014-07-04 23:57 ` Stephan Mueller [this message]
2014-07-05 0:09 ` Joe Perches
2014-07-05 0:15 ` Stephan Mueller
2014-07-05 0:24 ` Joe Perches
2014-07-05 0:27 ` Stephan Mueller
2014-06-28 20:04 ` [PATCH 4/4] DRBG: Call CTR DRBG DF function only once Stephan Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3856718.HehN4Xqlpl@myon.chronox.de \
--to=smueller@chronox.de \
--cc=dan.carpenter@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=joe@perches.com \
--cc=kbuild@01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).