Re: [PATCH 07/10] generic rwsem: implement down_read_critical() / up_read_critical()

From: David Howells
Date: Wed May 19 2010 - 09:22:40 EST

Michel Lespinasse <walken@xxxxxxxxxx> wrote:

> +void __sched down_read_critical(struct rw_semaphore *sem)
> +{
> + might_sleep();
> + rwsem_acquire_read(&sem->dep_map, 0, 0, _RET_IP_);
> +
> + LOCK_CONTENDED(sem, __down_read_trylock, __down_read_unfair);
> +
> + preempt_disable();

Shouldn't preemption really be disabled before __down_read_unfair() is called?
Otherwise you can get an unfair read on a sem and immediately get taken off
the CPU. Of course, this means __down_read_unfair() would have to deal with
that in the slow path:-/

Oh, and something else that occurs to me: Do unfair readers have to go at the
front of the wakeup queue? Can they be slightly less unfair and go either
before the first reader in the queue or at the back of the queue instead?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at