linux-kernel - Re: 2.6.23-rc2-mm1: rcutorture xtime usage

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]

Message-Id: <20070810101212.d59ce24a.akpm@linux-foundation.org>
Date:	Fri, 10 Aug 2007 10:12:12 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	paulmck@...ux.vnet.ibm.com
Cc:	Adrian Bunk <bunk@...nel.org>, Josh Triplett <josh@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.23-rc2-mm1: rcutorture xtime usage

On Fri, 10 Aug 2007 08:12:08 -0700 "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> wrote:

> > One used to use sched_clock() for this, then get frowned at.  Now we
> > have cpu_clock()...
> 
> Hmmm...  And cpu_clock() is not in 2.6.22, so must appear in some later
> release.  Which means that the rate of API change in this area is a
> bit high, so I should avoid it like the plague.

eh, it's been there for weeks.  It is dust-encrusted.

>  Therefore, I should
> look for some other convenient source of entropy.
> 
> One convenient source would the per-CPU statistics that rcutorture
> maintains.  Of course, a given CPU's RNG is nearly in lock-step with
> its own statistics, but not with the adjacent CPU's statistics...
> 
> I will send a patch.

Please use cpu_clock().  It ain't going away.
-
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/