Re: [PATCH] lockdep: make print_lock_name() robust against non-existing lock_class
From: Peter Zijlstra
Date: Thu Apr 16 2015 - 11:35:23 EST
On Thu, Apr 16, 2015 at 04:50:21PM +0200, Sebastian Andrzej Siewior wrote:
> Andreas confirmed that it works for him on v3.18 with minor adjustment.
>
> <---
> + struct held_lock lock = READ_ONCE(*hlock);
> + unsigned int class_idx = lock.class_idx;
> --->
>
I'm confused by the need for that. What was the failure with the
proposed patch?
--
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/