Please review, I'm afraid I could miss something. OTOH, this almost looks like a bug to me. And in fact I have a bug report which looks as if spin_unlock_wait() actually spins "forever" until the system panics, although most probably the are other problems in kernel/sched which lead to rq->lock contention.
Do we need a barrier() in arch_spin_unlock_wait() ? I guess no, and the current code doesn't have it. Perhaps it should use __ticket_lock_spinning() like arch_spin_lock() ? And probably we should add the lockdep annotations. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
