ERESOURCE acquisition logs?

NTDEV
1

Hello,

Is there a way to track where an ERESOURCE is currently held from (i.e. a actual address of acquisition, not just a thread from !locks output)?
One of our threads is holding a Cm lock, while it is calling into NTFS to complete a read. I am certain we didn’t acquire the lock from our driver, and it makes no sense to me why the thread would hold that lock, while in the FSD stack.

Regards, Dejan.

2

FYI, I know I can enable DV with Deadlock detection, but I don’t see !verifier outputting any acquisition logs then either (!verifier 0x200 says it is not enabled, even though it is, since !verifier says it is :))

0: kd> !deadlock

Deadlock Verifier Statistics:
-----------------------------

  Locks:                      0
  Threads:                    0
  Max Acquire Time:           0 (ticks)
  Max Release Time:           0 (ticks)
  Allocation Failures:        0
  Analyze Calls:              0
  Maximum Nodes Searched:     0
  Trimmed Nodes (due age):    0
  Trimmed Nodes (due count):  0
  Recursion Depth Limit:      4
  Recursion Depth Limit Hits: 0
  Search Nodes Limit:         1000
  Search Nodes Limit Hits:    0
  Stack Limit Hits:           0

No deadlock verifier issues. 
0: kd> !verifier 0x200
Critical Region log is empty. You have to enable Driver Verifier
for at least one driver to activate Critical Region tracking.