Re: [clocksource] INFO: possible irq lock inversion dependency detected

From: Jet Chen
Date: Tue Apr 08 2014 - 21:23:12 EST


On 04/08/2014 01:21 PM, Viresh Kumar wrote:
On 8 April 2014 09:29, Jet Chen <jet.chen@xxxxxxxxx> wrote:
(Sorry for previous bad format email)
Your patch on my testing branch in LKP system:
git://bee.sh.intel.com/git/tchen37/linux.git timer_debug3 got the below
dmesg.
FYI, I applied your patch on the top of commit
6378cb51af5f4743db0dcb3cbcf862eac5908754 - timer: don't migrate pinned
timers.

Hi Jet,

Thanks for your efforts. It looks like we must use spin_lock_irqsave() here.
And that's all we need to fix this issue..


spin_lock_irqsave() does fix this issue.

Tested-by: Jet Chen <jet.chen@xxxxxxxxx>

To get the right order in which patches must be applied (obviously with the
updates I have), please pick this branch:

git://git.linaro.org/people/viresh.kumar/linux.git isolate-cpusets

I hope this fixes the issues you were getting.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/