Thread (117 messages) 117 messages, 14 authors, 2013-02-19

Re: [PATCH v5 01/45] percpu_rwlock: Introduce the global reader-writer lock backend

From: David Howells <dhowells@redhat.com>
Date: 2013-02-11 12:42:17
Also in: linux-arm-kernel, linux-pm, linuxppc-dev, lkml, netdev

Srivatsa S. Bhat [off-list ref] wrote:
We can use global rwlocks as shown below safely, without fear of deadlocks:

Readers:

         CPU 0                                CPU 1
         ------                               ------

1.    spin_lock(&random_lock);             read_lock(&my_rwlock);


2.    read_lock(&my_rwlock);               spin_lock(&random_lock);
The lock order on CPU 0 is unsafe if CPU2 can do:

	write_lock(&my_rwlock);
	spin_lock(&random_lock);

and on CPU 1 if CPU2 can do:

	spin_lock(&random_lock);
	write_lock(&my_rwlock);

I presume you were specifically excluding these situations?

David
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help