From: Joe Perches <joe@perches.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH akpm-next] random32: minor cleanups and kdoc fix
Date: Wed, 12 Feb 2014 15:43:53 -0800 [thread overview]
Message-ID: <1392248633.2214.6.camel@joe-AO722> (raw)
In-Reply-To: <1392244982-20450-1-git-send-email-dborkman@redhat.com>
On Wed, 2014-02-12 at 23:43 +0100, Daniel Borkmann wrote:
> These are just some very minor and misc cleanups in the PRNG.
trivia:
> diff --git a/lib/random32.c b/lib/random32.c
[]
> @@ -30,7 +30,6 @@
>
> This affects the seeding procedure by imposing the requirement
> s1 > 1, s2 > 7, s3 > 15, s4 > 127.
> -
> */
Using normal comment block style
/*
*
*/
might be nicer
> #include <linux/types.h>
> @@ -75,15 +74,17 @@ EXPORT_SYMBOL(prandom_u32_state);
> */
> u32 prandom_u32(void)
> {
> - unsigned long r;
> struct rnd_state *state = &get_cpu_var(net_rand_state);
> - r = prandom_u32_state(state);
> + u32 res;
> +
> + res = prandom_u32_state(state);
Maybe:
u32 res = prandom_u32_state(state);
> @@ -201,9 +202,10 @@ static int __init prandom_init(void)
> for_each_possible_cpu(i) {
> struct rnd_state *state = &per_cpu(net_rand_state,i);
>
> - prandom_seed_very_weak(state, (i + jiffies) ^ random_get_entropy());
> + prandom_seed_very_weak(state, (i + jiffies) ^ (u32)random_get_entropy());
This (u32) cast is not necessary.
On 64 bit machines, the high 32 bits of random_get_entropy
are unnecessarily dropped/masked.
The compiler will cast the unsigned long result of the xor
back to u32 anyway.
prev parent reply other threads:[~2014-02-12 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 22:43 Daniel Borkmann
2014-02-12 23:43 ` Joe Perches [this message]
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=1392248633.2214.6.camel@joe-AO722 \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=dborkman@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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®