From: Michael Buesch <mb@bu3sch.de>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [HW_RNG] How to use generic rng in kernel space
Date: Tue, 1 Aug 2006 22:49:20 +0200 [thread overview]
Message-ID: <200608012249.20324.mb@bu3sch.de> (raw)
In-Reply-To: <20060801120937.69641.qmail@web25813.mail.ukl.yahoo.com>
On Tuesday 01 August 2006 14:09, moreau francis wrote:
> Hi
>
> I developped a HW RNG for a custom board and several
> other drivers are using it through a special entry I made.
> I was planning to move the code in order to use the generic
> the RNG layer but I encounter an issue.
>
> Currently it seems not possible for a driver to use HW RNG,
> because there's no entry point for that. Is that something
> deliberate ?
>
Never ever do that. Never use the data from a hardware RNG
directly. There is intentionally no interface to do so.
If you need random data in some driver, use the functions
in random.h to get random data.
The dataflow is as follows:
HW-RNG -> userspace RNGD (through /dev/hwrng) -> the daemon
checks it for sanity and puts it back into the kernel through
/dev/random -> Your driver gets the data from the /dev/random
entropy pools.
This is very neccesary, because your HW-RNG may fail and
so you may unintentionally use non-random data, if you use
the random data from the RNG directly.
The data _must_ go through userspace rngd, which does FIPS
sanity checks on the data.
> Another question about the implementation. If O_NONBLOCK
> flag is passed when opening /dev/hw_random, how does the
> read method ensure that the caller won't sleep since it calls
> mutex_lock_interruptible() function unconditiannaly ? I must
> miss something but don't know what...
I second Alan's answer here. ;)
--
Greetings Michael.
next prev parent reply other threads:[~2006-08-01 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 12:09 [HW_RNG] How to use generic rng in kernel space moreau francis
2006-08-01 13:29 ` Alan Cox
2006-08-01 13:28 ` Re : " moreau francis
2006-08-01 20:49 ` Michael Buesch [this message]
2006-08-04 13:00 ` moreau francis
2006-08-04 21:08 ` Michael Buesch
2006-08-05 1:44 ` Jeff Garzik
2006-08-08 15:39 ` Re : " moreau francis
2006-08-08 17:34 ` Michael Buesch
2006-08-09 10:02 ` Re : " moreau francis
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=200608012249.20324.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=francis_moreau2000@yahoo.fr \
--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