Lines Matching refs:userspace

72      are used to control what a process may do to a key from userspace, and
90      Similarly, when userspace wants to read back the contents of the key, if
97      	 Keys being requested from userspace will be in this state.
103 	 note saying that a previous call out to userspace failed, and acts as
111      (*) Revoked. A key is put in this state by userspace action. It can't be
137 	 blobs of data. These can be created, updated and read by userspace,
144 	 accessible to the kernel but not to userspace programs.
149 	 be created and updated from userspace, but the payload is only
197  (*) There's a system call interface by which userspace programs can create and
204      userspace to request a key that can't be found in a process's keyrings.
323 	U	Under construction by callback to userspace
375 When referring to a key directly, userspace programs should use the key's
436      userspace to create it.
544      than requested to userspace. If the buffer pointer is NULL then no copy
647      userspace if the buffer pointer is not NULL.
662      If the kernel calls back to userspace to complete the instantiation of a
663      key, userspace should use this call to supply data for the key before the
687      If the kernel calls back to userspace to complete the instantiation of a
688      key, userspace should use this call mark the key as negative before the
779      than requested to userspace. If the buffer pointer is NULL then no copy
807      kernel and resumes executing userspace.
892     the key from userspace. In that case, callout_string will be passed as an
1120      supplied by userspace into a pointer to the structure.
1327      key's payload into something a blob of data for userspace to deal with.
1337      as might happen when the userspace buffer is accessed.