linux-kernel - Re : [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-prev] [day] [month] [year] [list]

Message-ID: <20060809100253.78092.qmail@web25801.mail.ukl.yahoo.com>
Date:	Wed, 9 Aug 2006 10:02:53 +0000 (GMT)
From:	moreau francis <francis_moreau2000@...oo.fr>
To:	Michael Buesch <mb@...sch.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re : [HW_RNG] How to use generic rng in kernel space

Michael Buesch wrote:
> On Tuesday 08 August 2006 17:39, moreau francis wrote:
>> Michael Buesch wrote:
>>> So, if you have a special hwrng on your embedded board and you
>>> have some special driver in that board, why not interface
>>> directly from the driver to the hwrng-driver?
>> This is what I'm currently doing. I was just thinking to use the
>> new HW-RNG layer and drop common code...
>>
>>> This is all pretty special case.
>>> In the hwrng-driver you could still additionally do a
>>> hrwng_register() to export the functionality to
>>> userspace, though.
>>>
>> yes I would like to do that but there is a problem: I have no 
>> access to "rng_mutex" to synchronise hw accesses and I'm
>> wondering if there's any issue to use a mutex in driver init
>> code.
> 
> Use your own mutex or spinlock in the data_read callback
> and use that to serialize accesses to the hardware.
> 

I think I miss something there but I need to lock this whole
sequence when reading a random data:

    lock(hwrng);
    rng_data_present();
    rng_data_read();
    unlock(hwrng);

not only data_read callback. To do that I can only use "rng_mutex",
no ?

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/