Hi James,
This doesn't sound like a lock ordering issue or an exception to the
stated
lock ordering rules. In particular, there's no need to take the meta
lock
before dtrace or provider; rather, the meta lock must be taken before
either
of those locks if it is to be taken at all.
Is
I'm looking at a hang/stall while dtrace'ing on heavily loaded systems.
I've got the following scenario:
Kernel Thread A is waiting to acquire tthe dtrace_meta_lock
Kernel Thread B owns the dtrace_meta_lock, and is waiting on the
dtrace_provider_lock
Kernel Thread C owns the