can exclusively lock be owned by two thread at the same time?

2: kd> !locks FFFF9609741B9510

Resource @ 0xffff9609741b9510 Exclusively owned
Contention Count = 4
NumberOfSharedWaiters = 2
Threads: ffff9609741da080-01<> ffff96096edda140-01<> ffff960975c48080-01
1 total locks

This Command shows that resource @ 0xffff9609741b9510 is exclusively owned,
does this mean this lock is owned by thread at the same time right now?

ffff9609741da080-01<> ffff96096edda140-01<>

I don’t really understand what you’re asking. The resource is owned by one thread, and two others are waiting for it.

Thx @Tim_Roberts for your answering,
actually in this line Threads: ffff9609741da080-01<> ffff96096edda140-01<> ffff960975c48080-01 there are two asterisks in the <>s
and according to MSDN explanation from this https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/-locks---kdext--locks-
If a thread is followed by “”, that thread is one of the owners of the lock, so thread ffff9609741da080 and thread ffff96096edda140 are the owner of the locks, correct?

i don’t what happens to the posting, it always remove some of symbols, let me try to post a picture

Is this your lock? What kind of a lock is it? An exclusive lock should only have one owner.