Messages in this thread | | | Subject | Re: [PATCH 1/4] lockdep: lock_set_subclass() fix | From | Peter Zijlstra <> | Date | Tue, 08 Nov 2011 09:46:20 +0100 |
| |
On Tue, 2011-11-08 at 16:14 +0800, Yong Zhang wrote: > > But how do we deal with ->class_cache? Always set it in > loop_up_lock_class()?
Hrm.. good point, aside from that there's another problem as well, I think we can deal with the cache being NULL, but is memset() an atomic write? If not a read could observe an intermediate state and go funny.
I'm tempted to go with the pure kmemcheck_mark_initialized() thing for now.
| |