linux-kernel - Re: [PATCH] OF: Fixup resursive locking code paths

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]

Message-ID: <510FDD7B.7060903@windriver.com>
Date:	Mon, 4 Feb 2013 11:10:35 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	Grant Likely <grant.likely@...retlab.ca>,
	Rob Herring <rob.herring@...xeda.com>,
	<devicetree-discuss@...ts.ozlabs.org>,
	<linux-kernel@...r.kernel.org>, <linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH] OF: Fixup resursive locking code paths

On 13-02-04 05:48 AM, Thomas Gleixner wrote:
> On Fri, 25 Jan 2013, Paul Gortmaker wrote:
> 
>> From: Thomas Gleixner <tglx@...utronix.de>
>>
>> There is no real reason to use a rwlock for devtree_lock. It even
>> could be a mutex, but unfortunately it's locked from cpu hotplug
>> paths which can't schedule :(
>>
>> So it needs to become a raw lock on rt as well.  The devtree_lock would
>> be the only user of a raw_rw_lock, so we are better off cleaning up the
>> recursive locking paths which allows us to convert devtree_lock to a
>> read_lock.
> 
> Hmm. It's already a rw_lock. For RT we want to change that thing to a
> raw_spinlock.

Thanks for the reminder.  Part 2 sent now that the cleanup got OK'd.

Paul.
--

> 
> Thanks,
> 
> 	tglx
> 
--
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/