Re: Horrible regression with -CURRENT from "Don't busy-lock-loop inpreemptable spinlocks" patch

[Andrew Morton]

Chris Wedgwood <cw@xxxxxxxx> wrote:
>
> Linus,
> 
> The change below is causing major problems for me on a dual K7 with
> CONFIG_PREEMPT enabled (cset -x and rebuilding makes the machine
> usable again).
> 
> ...
> +BUILD_LOCK_OPS(spin, spinlock_t, spin_is_locked);
> +BUILD_LOCK_OPS(read, rwlock_t, rwlock_is_locked);
> +BUILD_LOCK_OPS(write, rwlock_t, spin_is_locked);

If you replace the last line with

	BUILD_LOCK_OPS(write, rwlock_t, rwlock_is_locked);

does it help?
-
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/