| 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: <20150319150111.778d21d3@gandalf.local.home> Date: Thu, 19 Mar 2015 15:01:11 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Daniel Thompson <daniel.thompson@...aro.org> Cc: Peter Zijlstra <peterz@...radead.org>, linux-arm-kernel@...ts.infradead.org, Catalin Marinas <catalin.marinas@....com>, Will Deacon <will.deacon@....com>, linux-kernel@...r.kernel.org, patches@...aro.org, linaro-kernel@...ts.linaro.org, John Stultz <john.stultz@...aro.org>, Sumit Semwal <sumit.semwal@...aro.org>, Marc Zyngier <marc.zyngier@....com>, Andrew Thoelke <andrew.thoelke@....com>, Dongdong Deng <dongdong.deng@...driver.com> Subject: Re: [RFC PATCH 2/7] printk: Simple implementation for NMI backtracing On Thu, 19 Mar 2015 18:48:10 +0000 Daniel Thompson <daniel.thompson@...aro.org> wrote: \ > The barrier was not intended to have anything to do with put_cpu() > either though since the barrier was added before put_cpu() arrived: > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=554ec063982752e9a569ab9189eeffa3d96731b2 > > There's nothing in the commit comment explaining the barrier and I > really can't see what it is for. > Looks like it wasn't needed then either. -- Steve -- 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