| 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
| ||
|
Message-ID: <20070810203055.GE8511@linux.vnet.ibm.com> Date: Fri, 10 Aug 2007 13:30:55 -0700 From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com> To: Andrew Morton <akpm@...ux-foundation.org> 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, Aug 10, 2007 at 10:12:12AM -0700, Andrew Morton wrote: > 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. D'accord... Thanx, Paul - 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/
Powered by blists - more mailing lists