Lines Matching full:held

46 - 'ever held in STATE context'
47 - 'ever held as readlock in STATE context'
48 - 'ever held with STATE enabled'
49 - 'ever held as readlock with STATE enabled'
170 any rule violation between the new lock and any of the held locks.
238 must be held: lockdep_assert_held*(&lock) and lockdep_*pin_lock(&lock).
241 particular lock is held at a certain time (and generate a WARN() otherwise).
329 held locks is maintained, and a lightweight 64-bit hash value is
523 , which means lockdep has seen L1 held before L2 held in the same context at runtime.
524 And in deadlock detection, we care whether we could get blocked on L2 with L1 held,
622 held by different CPU/tasks.
625 in L1 -> L2, however since L2 is already held by another CPU/task, plus L1 ->
643 a lock held by P2, and P2 is waiting for a lock held by P3, ... and Pn is waiting
644 for a lock held by P1. Let's name the lock Px is waiting as Lx, so since P1 is waiting