linux-kernel - Re: [PATCH 2/2] lockdep: Don't only check recursive read locks once in a sequence

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: <20091120005743.GJ4967@nowhere>
Date:	Fri, 20 Nov 2009 01:57:46 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Lai Jiangshan <laijs@...fujitsu.com>, Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ming Lei <tom.leiming@...il.com>
Subject: Re: [PATCH 2/2] lockdep: Don't only check recursive read locks
	once in a sequence

On Thu, Nov 19, 2009 at 06:13:48PM +0100, Peter Zijlstra wrote:
> On Thu, 2009-11-19 at 16:55 +0100, Frederic Weisbecker wrote:
> > And btw I
> > don't understand why rwsem read locks are not considered as
> > recursive in lockdep. 
> 
> Because they're not.
> 
> rwsems are FIFO fair, so a double read can deadlock when there's a
> pending writer inbetween.
> 


Aah ok. That's the subtle thing I was missing :)

Thanks.

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