[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170616154245.5fry4lclgmp3gfdi@linutronix.de>
Date: Fri, 16 Jun 2017 17:42:45 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: Tony Lindgren <tony@...mide.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-omap@...r.kernel.org,
Ingo Molnar <mingo@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will.deacon@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Russell King <linux@...linux.org.uk>
Subject: Re: [PATCH] ARM/hw_breakpoint: Fix possible recursive locking for
arch_hw_breakpoint_init
On 2017-06-16 01:22:38 [-0700], Tony Lindgren wrote:
> Recent change to use cpuhp_setup_state_cpuslocked() with commit
> fe2a5cd8aa03 ("ARM/hw_breakpoint: Use cpuhp_setup_state_cpuslocked()")
> missed to change the related paired cpuhp_remove_state_nocalls_cpuslocked().
>
> Now if arch_hw_breakpoint_init() fails, we get "WARNING: possible recursive
> locking detected" on the exit path.
>
> Fixes: fe2a5cd8aa03 ("ARM/hw_breakpoint: Use
> cpuhp_setup_state_cpuslocked()")
> Cc: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
> Cc: Ingo Molnar <mingo@...nel.org>
> Cc: Mark Rutland <mark.rutland@....com>
> Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Will Deacon <will.deacon@....com>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Russell King <linux@...linux.org.uk>
> Cc: linux-arm-kernel@...ts.infradead.org
> Signed-off-by: Tony Lindgren <tony@...mide.com>
Acked-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Thank you.
Sebastian
Powered by blists - more mailing lists