linux-kernel - [HW_RNG] How to use generic rng in kernel space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060801120937.69641.qmail@web25813.mail.ukl.yahoo.com>
Date:	Tue, 1 Aug 2006 12:09:37 +0000 (GMT)
From:	moreau francis <francis_moreau2000@...oo.fr>
To:	mb@...sch.de
Cc:	linux-kernel@...r.kernel.org
Subject: [HW_RNG] How to use generic rng in kernel space

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 ?

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...

Thanks

Francis

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/