Lines Matching refs:payload
26 - Notes on accessing payload contents
46 - A payload.
78 (*) Each key can have a payload. This is a quantity of data that represent the
83 Having a payload is not required; and the payload can, in fact, just be a
87 called with a blob of data, and that then creates the key's payload in
92 attached payload back into a blob of data.
132 be given a payload when created.
136 A key of this type has a description and a payload that are arbitrary
142 Like a "user" key, a "logon" key has a payload that is an arbitrary
149 be created and updated from userspace, but the payload is only
185 amount of description and payload space that can be consumed.
225 This permits a key's payload to be viewed or a keyring's list of linked
230 This permits a key's payload to be instantiated or updated, or it allows a
296 It is not possible to view the payload of the key this way, though some
394 (*) Create a new key of given type, description and payload and add it to the
398 const void *payload, size_t plen,
402 in the keyring, this will try to update it with the given payload, or it
409 description, and to instantiate it with the supplied payload and attach it
415 of the payload.
417 The payload is optional, and the pointer can be NULL if not required by
418 the type. The payload is plen in size, and plen can be zero for an empty
419 payload.
422 as the description (or NULL) and setting the payload to NULL.
489 long keyctl(KEYCTL_UPDATE, key_serial_t key, const void *payload,
492 This will try to update the specified key with the given payload, or it
497 The payload is of length plen, and may be absent or empty as for
540 payload data) as a string in the buffer provided.
631 (*) Read the payload data from a key:
636 This function attempts to read the payload data from the specified key
656 const void *payload, size_t plen,
674 The payload and plen arguments describe the payload data as for add_key().
676 The payload_iov and ioc arguments describe the payload data in an iovec
878 When accessing a key's payload contents, certain precautions must be taken to
880 payload contents" for more information.
1052 The simplest payload is just data stored in key->payload directly. In this
1053 case, there's no need to indulge in RCU or locking when accessing the payload.
1055 More complex payload contents must be allocated and pointers to them set in the
1056 key->payload.data[] array. One of the following ways must be selected to
1061 If the key type does not have a modify method, then the key's payload can
1067 The semaphore could be used to govern access to the payload and to control
1068 the payload pointer. It must be write-locked for modifications and would
1088 Note that only the key type should ever modify a key's payload.
1090 Furthermore, an RCU controlled payload must hold a struct rcu_head for the
1091 use of call_rcu() and, if the payload is of variable size, the length of
1092 the payload. key->datalen cannot be relied upon to be consistent with the
1093 payload just dereferenced if the key's semaphore is not held.
1095 Note that key->payload.data[0] has a shadow that is marked for __rcu
1096 usage. This is called key->payload.rcu_data0. The following accessors
1125 This is optional - it supplies the default payload data length as
1126 contributed to the quota. If the key type's payload is always or almost
1147 This optional method permits the key type to attempt to parse payload
1153 union key_payload payload;
1161 the payload blob parameters; quotalen will be filled in with the default
1165 If a description can be proposed from the payload contents, that should be
1169 The method can attach anything it likes to payload. This is merely passed
1181 and payload fields of the key_preparsed_payload struct as filled in by the
1188 This method is called to attach a payload to a key during construction.
1189 The payload attached need not bear any relation to the data passed to this
1192 The prep->data and prep->datalen fields will define the original payload
1198 This method does not have to lock the key in order to attach a payload.
1205 prep->payload.data[] to key->payload.data[], with RCU-safe assignment on
1206 the first element. It will then clear prep->payload.data[] so that the
1213 It is called to update a key's payload from the blob of data provided.
1215 The prep->data and prep->datalen fields will define the original payload
1224 but this only deters other writers; any changes to the key's payload must
1226 the old payload.
1288 This method is optional. It is called to discard part of the payload
1298 This method is optional. It is called to discard the payload data on a key
1301 This method does not need to lock the key to access the payload; it can
1311 summarise a key's description and payload in text form.
1314 should be used to read the payload pointer if the payload is to be
1316 contents of the payload.
1327 key's payload into something a blob of data for userspace to deal with.
1335 prevent the key's payload changing. It is not necessary to use RCU locking
1336 when accessing the key's payload. It is safe to sleep in this method, such