[PATCH RT] rwlock: be more conservative in locking reader_lock_count
From: Steven Rostedt
Date: Tue Jul 15 2008 - 20:28:22 EST
John Stultz was hitting one of the rwlock warnings. This was indeed a bug.
The assumption of trying not to take locks was incorrect and prone to
bugs. This patch adds a few locks around the needed areas to correct the
issue and make the code a bit more robust.
Signed-off-by: Steven Rostedt <srostedt@xxxxxxxxxx>
---
kernel/rtmutex.c | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
Index: linux-2.6.24.7-rt-73/kernel/rtmutex.c
===================================================================
--- linux-2.6.24.7-rt-73.orig/kernel/rtmutex.c 2008-07-14 22:27:13.000000000 -0400
+++ linux-2.6.24.7-rt-73/kernel/rtmutex.c 2008-07-14 22:30:54.000000000 -0400
@@ -1137,16 +1137,13 @@ rt_rwlock_update_owner(struct rw_mutex *
if (own == RT_RW_READER)
return;
- /*
- * We don't need to grab the pi_lock to look at the reader list
- * since we hold the rwm wait_lock. We only care about the pointer
- * to this lock, and we own the wait_lock, so that pointer
- * can't be changed.
- */
+ spin_lock(&own->pi_lock);
for (i = own->reader_lock_count - 1; i >= 0; i--) {
if (own->owned_read_locks[i].lock == rwm)
break;
}
+ spin_unlock(&own->pi_lock);
+
/* It is possible the owner didn't add it yet */
if (i < 0)
return;
@@ -1453,7 +1450,6 @@ __rt_read_fasttrylock(struct rw_mutex *r
current->owned_read_locks[reader_count].count = 1;
} else
WARN_ON_ONCE(1);
- spin_unlock(¤t->pi_lock);
/*
* If this task is no longer the sole owner of the lock
* or someone is blocking, then we need to add the task
@@ -1463,12 +1459,16 @@ __rt_read_fasttrylock(struct rw_mutex *r
struct rt_mutex *mutex = &rwm->mutex;
struct reader_lock_struct *rls;
+ /* preserve lock order, we only need wait_lock now */
+ spin_unlock(¤t->pi_lock);
+
spin_lock(&mutex->wait_lock);
rls = ¤t->owned_read_locks[reader_count];
if (!rls->list.prev || list_empty(&rls->list))
list_add(&rls->list, &rwm->readers);
spin_unlock(&mutex->wait_lock);
- }
+ } else
+ spin_unlock(¤t->pi_lock);
local_irq_restore(flags);
return 1;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/