mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benoit Boissinot <bboissin@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Jack Lloyd <lloyd@randombit.net>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Bug in random32.c: all-zero outputs with probability 1/2^32, other seeding bugs
Date: Wed, 2 Jul 2008 01:19:27 +0200	[thread overview]
Message-ID: <20080701231927.GW7647@pirzuine> (raw)
In-Reply-To: <20080619153045.GC1455@randombit.net>

[who maintains random32.c ?]

On Thu, Jun 19, 2008 at 5:30 PM, Jack Lloyd <lloyd@randombit.net> wrote:
> Hi,
>
> There appears to be an error in how random seeding is done in the
> random32.c RNG. I am looking at 2.6.25.7.
>
[snip]
>
> An easy and straightforward fix for this that doesn't require changing
> any interfaces is to add
>  s &= 0xFFFFFFFF;
> before the check in __set_random32, which ensures this condition will
> be caught by the check. Alternately, you could replace the check for
> s == 0 with some logic like:
>  if((s & 0xFFFFFFFF) == 0)
>     s += 1;
> since just chopping the seed to 32 bits does throw away some of your
> seed input (with sizeof(long) == 8, at least; doesn't make any
> difference for sizeof(long) == 4)
>

I think it is cleaner to change the interface to account for long != u32

The rest of your patch (ensuring values are big enough) looks valid to me.

Signed-off-by: Benoit Boissinot <benoit.boissinot@ens-lyon.org>

diff -r ced66ca0044f lib/random32.c
--- a/lib/random32.c	Mon Jun 30 08:58:09 2008 -0700
+++ b/lib/random32.c	Wed Jul 02 01:13:12 2008 +0200
@@ -56,7 +56,7 @@
 	return (state->s1 ^ state->s2 ^ state->s3);
 }

-static void __set_random32(struct rnd_state *state, unsigned long s)
+static void __set_random32(struct rnd_state *state, u32 s)
 {
 	if (s == 0)
 		s = 1;      /* default seed is 1 */
@@ -84,7 +84,7 @@
  */
 u32 random32(void)
 {
-	unsigned long r;
+	u32 r;
 	struct rnd_state *state = &get_cpu_var(net_rand_state);
 	r = __random32(state);
 	put_cpu_var(state);
@@ -122,7 +122,7 @@

 	for_each_possible_cpu(i) {
 		struct rnd_state *state = &per_cpu(net_rand_state,i);
-		__set_random32(state, i + jiffies);
+		__set_random32(state, (u32) i + jiffies);
 	}
 	return 0;
 }
@@ -135,7 +135,7 @@
 static int __init random32_reseed(void)
 {
 	int i;
-	unsigned long seed;
+	u32 seed;

 	for_each_possible_cpu(i) {
 		struct rnd_state *state = &per_cpu(net_rand_state,i);

  reply	other threads:[~2008-07-01 23:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 15:30 Jack Lloyd
2008-07-01 23:19 ` Benoit Boissinot [this message]
2008-07-02  0:34   ` Andrew Morton
2008-07-02  3:22     ` Matt Mackall
2008-07-02 16:40       ` Stephen Hemminger
2008-07-02  6:38   ` Jan Engelhardt

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=20080701231927.GW7647@pirzuine \
    --to=bboissin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lloyd@randombit.net \
    /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

all inboxes | Powered by JetHome®