linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warning after merge of the random tree
Date: Mon, 23 Sep 2013 14:39:24 +1000	[thread overview]
Message-ID: <20130923143924.730ce3cbffbebdb7f82ce2cf@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1379 bytes --]

Hi Ted,

After merging the random tree, today's linux-next build (powerpc64
allnoconfig) produced this warning:

In file included from include/linux/kernel.h:10:0,
                 from include/linux/sched.h:15,
                 from include/linux/utsname.h:5,
                 from drivers/char/random.c:238:
drivers/char/random.c: In function 'add_interrupt_randomness':
include/linux/bitops.h:96:2: warning: 'input[3]' may be used uninitialized in this function [-Wmaybe-uninitialized]
  return (word << shift) | (word >> (32 - shift));
  ^
drivers/char/random.c:827:10: note: 'input[3]' was declared here
  __u32   input[4], cycles = random_get_entropy();
          ^
In file included from include/linux/kernel.h:10:0,
                 from include/linux/sched.h:15,
                 from include/linux/utsname.h:5,
                 from drivers/char/random.c:238:
include/linux/bitops.h:96:2: warning: 'input[2]' may be used uninitialized in this function [-Wmaybe-uninitialized]
  return (word << shift) | (word >> (32 - shift));
  ^
drivers/char/random.c:827:10: note: 'input[2]' was declared here
  __u32   input[4], cycles = random_get_entropy();
          ^

Probably introduced by commit d5693ae494f2 ("random: speed up the
fast_mix function by a factor of four").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-09-23  4:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23  4:39 Stephen Rothwell [this message]
2013-09-23  4:42 ` linux-next: build warning after merge of the random tree Stephen Rothwell
2014-07-21  7:49 Stephen Rothwell
2017-02-01  6:09 Stephen Rothwell
2018-06-08  3:37 Stephen Rothwell
2018-06-18  3:35 ` Stephen Rothwell
2018-06-18  5:29   ` Tobin C. Harding
2018-07-10  7:26     ` Stephen Rothwell
2018-07-16  5:52 Stephen Rothwell
2020-03-02  3:44 Stephen Rothwell
2020-03-06  4:53 ` Stephen Rothwell
2020-03-10 12:17   ` Mark Rutland
2020-03-10 14:46     ` Theodore Y. Ts'o
2020-03-16  5:59       ` Stephen Rothwell
2020-03-19  3:30         ` Theodore Y. Ts'o

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=20130923143924.730ce3cbffbebdb7f82ce2cf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).