[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a24804730805162155m72e6b40aweb8822515c880c50@mail.gmail.com>
Date: Fri, 16 May 2008 21:55:20 -0700
From: "Chris Peterson" <cpeterso@...terso.com>
To: "Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc: "Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>,
"Jeff Garzik" <jeff@...zik.org>,
"Kok, Auke" <auke-jan.h.kok@...el.com>,
"Rick Jones" <rick.jones2@...com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/net: remove network drivers' last few uses of IRQF_SAMPLE_RANDOM
> If they don't need that level of security they can use /dev/urandom.
> Piping network randomness into /dev/urandom is probably quite sensible
> but not into /dev/random.
If there was an IRQF_SAMPLE_DUBIOUS or IRQF_SAMPLE_URANDOM for network
device IRQs to feed /dev/urandom, are there any other IRQs that should
use it instead of IRQF_SAMPLE_RANDOM?
>From a cursory search, it seems like:
* network drivers could use IRQF_SAMPLE_URANDOM
* all (?) other device drivers could use IRQF_SAMPLE_RANDOM
* and timer IRQs should not use either?
chris
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists