Searched refs:revocation (Results 1 – 6 of 6) sorted by relevance
44 revocation: Completion, field233 revocation <- Completion::new(), in new()272 inner.revocation.complete_all(); in devres_node_release()277 inner.revocation.wait_for_completion(); in devres_node_release()375 self.inner.revocation.complete_all(); in drop()387 self.inner.revocation.wait_for_completion(); in drop()
74 or a block revocation list. A finished transaction always ends with a154 - Block revocation records. This speeds up recovery by enabling the307 - Journal has block revocation records. (JBD2_FEATURE_INCOMPAT_REVOKE)521 A revocation block is used to prevent replay of a block in an earlier531 the removal of all existing revocation records for that block.564 JBD2_FEATURE_INCOMPAT_CSUM_V3 are set, the end of the revocation578 - Checksum of the journal UUID + revocation block
33 their next access. The revocation and subsequent recreation of
84 revocation, rescission, cancellation, termination, or any other legal or
212 -> Interrupt results in schedule and grant revocation
187 Rules are evaluated top-to-bottom. As a result, any revocation rules,647 This property can be utilized for authorization or revocation of