linux-kernel - Re: [PATCH] ARM64: smp: Silence suspicious RCU usage with ipi tracepoints

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:	Wed, 24 Jun 2015 14:59:30 -0700
From:	Stephen Boyd <sboyd@...eaurora.org>
To:	Peter Zijlstra <peterz@...radead.org>
CC:	Catalin Marinas <catalin.marinas@....com>,
	Will Deacon <will.deacon@....com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	John Stultz <john.stultz@...aro.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Nicolas Pitre <nicolas.pitre@...aro.org>
Subject: Re: [PATCH] ARM64: smp: Silence suspicious RCU usage with ipi tracepoints

On 06/24/2015 02:29 PM, Peter Zijlstra wrote:
> On Wed, Jun 24, 2015 at 01:14:18PM -0700, Stephen Boyd wrote:
>> John Stultz reported an RCU splat on ARM with ipi trace events
>> enabled. It looks like the same problem exists on ARM64.
>>
>> At this point in the IPI handling path we haven't called
>> irq_enter() yet, so RCU doesn't know that we're about to exit
>> idle and properly warns that we're using RCU from an idle CPU.
>> Use trace_ipi_entry_rcuidle() instead of trace_ipi_entry() so
>> that RCU is informed about our exit from idle.
> I have a problem with $subject. It says 'silence', whereas afaict this
> fixes an actual bug, so it should be 'fixes'.

Fair enough. I can resend or whoever applies this patch can
s/Silence/Fix/ on the $subject.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

--
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/