Lines Matching refs:must

57  (*) Each key is of a defined "type". Types must be registered inside the
146 	 The description can be arbitrary, but must be prefixed with a non-zero
241      keyring to a key, a process must have Write permission on the keyring and
267 creation request.  Tasks must be granted explicit permission to assign a
404      type. The process must also have permission to write to the key to be able
429      Any other type must have been registered with the kernel in advance by a
481      To attach to a named keyring, the keyring must have search permission for
494      type. The process must also have permission to write to the key to be able
547      A process must have view permission on the key for this function to be
568      process must have write permission on the keyring, and it must be a
580      This function creates a link from the keyring to the key. The process must
581      have write permission on the keyring and must have link permission on the
601      ignored. The process must have write permission on the keyring.
617      The process must have search permission on the top level keyring, or else
637      into the buffer. The process must have read permission on the key to
667      The process must have write access on the key to be able to instantiate
668      it, and the key must be uninstantiated.
691      The process must have write access on the key to be able to instantiate
692      it, and the key must be uninstantiated.
742      The process must have attribute modification access on a key to set its
786      A process must have view permission on the key for this function to be
798      The calling process must have the same ownership as its parent, the
799      keyring must have the same ownership as the calling process, the calling
800      process must have LINK permission on the keyring and the active LSM module
823      A process must have search permission on the key for this function to be
842 To access the key manager, the following header must be #included:
873      possession information (which must be true or false).
878 When accessing a key's payload contents, certain precautions must be taken to
1055 More complex payload contents must be allocated and a pointer to them set in
1056 key->payload.data. One of the following ways must be selected to access the
1068      the payload pointer. It must be write-locked for modifications and would
1074      RCU must be used when the semaphore isn't already held; if the semaphore
1076      semaphore must still be used to serialise modifications to the key. The
1090      Furthermore, an RCU controlled payload must hold a struct rcu_head for the
1212      memory allocation must be done first.
1215      but this only deters other writers; any changes to the key's payload must
1216      be made under RCU conditions, and call_rcu() must be used to dispose of
1250       	  keys in the keyring until one is matched.  This must be used for any
1344      following function must be called under all circumstances to complete the
1356      caller of request_key*().  complete_request_key() must be called prior to