linux-kernel - Re: [PATCHv2] ARM: omap2+: omap_hwmod: Set unique lock_class

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] [day] [month] [year] [list]

Date:	Tue, 10 Feb 2015 20:20:36 +0000 (UTC)
From:	Paul Walmsley <paul@...an.com>
To:	Peter Ujfalusi <peter.ujfalusi@...com>
cc:	tony@...mide.com, peterz@...radead.org, linux-omap@...r.kernel.org,
	mingo@...hat.com, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCHv2] ARM: omap2+: omap_hwmod: Set unique lock_class_key
 per hwmod

On Tue, 10 Feb 2015, Peter Ujfalusi wrote:

> Add struct lock_class_key to omap_hwmod struct and use it to set unique
> lockdep class per hwmod.
> This will ensure that lockdep will know that each omap_hwmod->_lock should
> be treated as separate class and will not give false warning about deadlock
> or other issues due to nested use of hwmods.
> DRA7x's ATL hwmod is one example for this since McASP can select ATL clock
> as functional clock, which will trigger nested oh->_lock usage. This will
> trigger false warning from lockdep validator as it is dealing with classes
> and for it all hwmod clocks are the same class.
> 
> Suggested-by: Peter Zijlstra <peterz@...radead.org>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@...com>

Thanks queued for v3.20-rc.


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