linux-kernel - Re: [PATCH] Make rcutorture RNG use temporal entropy

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 17 Aug 2007 11:53:56 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	bunk@...nel.org, josh@...nel.org, linux-kernel@...r.kernel.org,
	mingo@...e.hu
Subject: Re: [PATCH] Make rcutorture RNG use temporal entropy

On Wed, 15 Aug 2007 19:49:04 -0700
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:

> Repost of http://lkml.org/lkml/2007/8/10/472 made available by request.
> 
> The locking used by get_random_bytes() can conflict with the
> preempt_disable() and synchronize_sched() form of RCU.  This patch changes
> rcutorture's RNG to gather entropy from the new cpu_clock() interface
> (relying on interrupts, preemption, daemons, and rcutorture's reader
> thread's rock-bottom scheduling priority to provide useful entropy),
> and also adds and EXPORT_SYMBOL_GPL() to make that interface available
> to GPLed kernel modules such as rcutorture.
> 
> Passes several hours of rcutorture.

Please explain what "conflict with" means so that I can work out if
this is a needed-in-2.6.23 change, thanks.
-
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/