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

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:	Tue, 8 Apr 2014 10:51:02 +0530
From:	Viresh Kumar <viresh.kumar@...aro.org>
To:	abd38155f8293923de5953cc063f9e2d7ecb3f04.1396679170.git.viresh.kumar@...aro.org
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	Jet Chen <jet.chen@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [clocksource] INFO: possible irq lock inversion dependency detected

On 8 April 2014 09:29, Jet Chen <jet.chen@...el.com> 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..

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/