| 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: <25275.1226055568@redhat.com> Date: Fri, 07 Nov 2008 10:59:28 +0000 From: David Howells <dhowells@...hat.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: dhowells@...hat.com, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>, Linus Torvalds <torvalds@...ux-foundation.org>, Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <a.p.zijlstra@...llo.nl>, linux-kernel@...r.kernel.org, Nicolas Pitre <nico@....org>, Ralf Baechle <ralf@...ux-mips.org>, benh@...nel.crashing.org, paulus@...ba.org, David Miller <davem@...emloft.net>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, Steven Rostedt <rostedt@...dmis.org>, linux-arch@...r.kernel.org Subject: Re: [RFC patch 08/18] cnt32_to_63 should use smp_rmb() Andrew Morton <akpm@...ux-foundation.org> wrote: > I mean, the darned thing is called from sched_clock(), which can be > concurrently called on separate CPUs and which can be called from > interrupt context (with an arbitrary nesting level!) while it was running > in process context. > > Who let that thing into Linux? Having crawled all over it, and argued with Nicolas and Panasonic about it, I think it's safe in sched_clock(), provided sched_clock() never gets preempted - which appears to be the case. David -- 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