Recursive call to ExAcquireResourceExclusiveLite after ExAcquireResourceSharedLite on the same resource from the same thread. Is it guaranteed to deadlock?

WINDBG
1

Pretty much what the title says. I'm trying to understand the cause of a bugcheck by analyzing a crash dump and I see that pattern from the !locks command in WinDbg.

2

yes it is a guaranteed deadlock.

3

That's what I thought. Thanks