Function report

Linux Kernel

v5.5.9

Brick Technologies Co., Ltd

Source Code:security\keys\keyring.c Create Date:2022-07-28 18:18:45
Last Modify:2020-03-12 14:18:49 Copyright©Brick
home page Tree
Annotation kernel can get tool activityDownload SCCTChinese

Name:Garbage collect pointers from a keyring.* Not called with any locks held. The keyring's key struct will not be* deallocated under us as only our caller may deallocate it.

Proto:void keyring_gc(struct key *keyring, time64_t limit)

Type:void

Parameter:

TypeParameterName
struct key *keyring
time64_tlimit
1718  kenter("%x{%s}", key serial number , description ? : "")
1720  If status flags (change with bitops) & ( 1 << set if key has been invalidated | 1 << set if key had been revoked ) Then Go to dont_gc
1725  _read_lock() - mark the beginning of an RCU read-side critical section* When synchronize_rcu() is invoked on one CPU while other CPUs* are within RCU read-side critical sections, then the* synchronize_rcu() is guaranteed to block until after all the other
1726  result = assoc_array_iterate - Pass all objects in the array to a callback*@array: The array to iterate over.*@iterator: The callback function.*@iterator_data: Private data for the callback function.* Iterate over all the objects in an associative array
1728  _read_unlock() - marks the end of an RCU read-side critical section.* In most situations, rcu_read_unlock() is immune from deadlock.* However, in kernels built with CONFIG_RCU_BOOST, rcu_read_unlock()
1729  If (result == true) Then Go to do_gc
1732  dont_gc :
1733  kleave(" [no gc]")
1734  Return
1736  do_gc :
1737  lock for writing
1738  assoc_array_gc - Garbage collect an associative array
1740  lease a write lock
1741  kleave(" [gc]")