[MIPS] Change libgcc-style functions from lib-y to obj-y

[linux-drm-fsl-dcu.git] / Documentation / keys.txt

diff --git a/Documentation/keys.txt b/Documentation/keys.txt
index e373f02128434277bc53098185b393df0a7c36d5..81d9aa09729811e7ca2cec3500e796d8a583c600 100644 (file)
--- a/Documentation/keys.txt
+++ b/Documentation/keys.txt
@@ -304,7 +304,7 @@ about the status of the key service:
        R       Revoked
        D       Dead
        Q       Contributes to user's quota
        R       Revoked
        D       Dead
        Q       Contributes to user's quota

-       U       Under contruction by callback to userspace
+       U       Under construction by callback to userspace

        N       Negative key
 
      This file must be enabled at kernel configuration time as it allows anyone
        N       Negative key
 
      This file must be enabled at kernel configuration time as it allows anyone


@@ -671,7 +671,7 @@ The keyctl syscall functions are:
 
      Note that this setting is inherited across fork/exec.
 
 
      Note that this setting is inherited across fork/exec.
 

-     [1] The default default is: the thread keyring if there is one, otherwise
+     [1] The default is: the thread keyring if there is one, otherwise

      the process keyring if there is one, otherwise the session keyring if
      there is one, otherwise the user default session keyring.
 
      the process keyring if there is one, otherwise the session keyring if
      there is one, otherwise the user default session keyring.
 


@@ -708,14 +708,14 @@ The keyctl syscall functions are:
 
      If the specified key is 0, then any assumed authority will be divested.
 
 
      If the specified key is 0, then any assumed authority will be divested.
 

-     The assumed authorititive key is inherited across fork and exec.
+     The assumed authoritative key is inherited across fork and exec.

 
 
 ===============
 KERNEL SERVICES
 ===============
 
 
 
 ===============
 KERNEL SERVICES
 ===============
 

-The kernel services for key managment are fairly simple to deal with. They can
+The kernel services for key management are fairly simple to deal with. They can

 be broken down into two areas: keys and key types.
 
 Dealing with keys is fairly straightforward. Firstly, the kernel service
 be broken down into two areas: keys and key types.
 
 Dealing with keys is fairly straightforward. Firstly, the kernel service


@@ -859,6 +859,18 @@ payload contents" for more information.
        void unregister_key_type(struct key_type *type);
 
 
        void unregister_key_type(struct key_type *type);
 
 

+Under some circumstances, it may be desirable to desirable to deal with a
+bundle of keys.  The facility provides access to the keyring type for managing
+such a bundle:
+
+       struct key_type key_type_keyring;
+
+This can be used with a function such as request_key() to find a specific
+keyring in a process's keyrings.  A keyring thus found can then be searched
+with keyring_search().  Note that it is not possible to use request_key() to
+search a specific keyring, so using keyrings in this way is of limited utility.
+
+

 ===================================
 NOTES ON ACCESSING PAYLOAD CONTENTS
 ===================================
 ===================================
 NOTES ON ACCESSING PAYLOAD CONTENTS
 ===================================