Lines Matching full:payload
35 - A payload.
67 * Each key can have a payload. This is a quantity of data that represent the
72 Having a payload is not required; and the payload can, in fact, just be a
76 called with a blob of data, and that then creates the key's payload in
81 attached payload back into a blob of data.
120 be given a payload when created.
124 A key of this type has a description and a payload that are arbitrary
130 Like a "user" key, a "logon" key has a payload that is an arbitrary
137 be created and updated from userspace, but the payload is only
173 amount of description and payload space that can be consumed.
212 This permits a key's payload to be viewed or a keyring's list of linked
217 This permits a key's payload to be instantiated or updated, or it allows a
281 It is not possible to view the payload of the key this way, though some
379 * Create a new key of given type, description and payload and add it to the
383 const void *payload, size_t plen,
387 in the keyring, this will try to update it with the given payload, or it
394 description, and to instantiate it with the supplied payload and attach it
400 of the payload.
402 The payload is optional, and the pointer can be NULL if not required by
403 the type. The payload is plen in size, and plen can be zero for an empty
404 payload.
407 as the description (or NULL) and setting the payload to NULL.
478 long keyctl(KEYCTL_UPDATE, key_serial_t key, const void *payload,
481 This will try to update the specified key with the given payload, or it
486 The payload is of length plen, and may be absent or empty as for
529 payload data) as a string in the buffer provided.
641 * Read the payload data from a key::
646 This function attempts to read the payload data from the specified key
666 const void *payload, size_t plen,
684 The payload and plen arguments describe the payload data as for add_key().
686 The payload_iov and ioc arguments describe the payload data in an iovec
906 verification or constraints on key payload. If the requested key type is
1140 When accessing a key's payload contents, certain precautions must be taken to
1142 payload contents" for more information.
1285 added to, the key type, the payload of the key being added, and data to be
1287 this is called between payload preparsing and actual key creation. The
1328 Notes On Accessing Payload Contents
1331 The simplest payload is just data stored in key->payload directly. In this
1332 case, there's no need to indulge in RCU or locking when accessing the payload.
1334 More complex payload contents must be allocated and pointers to them set in the
1335 key->payload.data[] array. One of the following ways must be selected to
1340 If the key type does not have a modify method, then the key's payload can
1346 The semaphore could be used to govern access to the payload and to control
1347 the payload pointer. It must be write-locked for modifications and would
1367 Note that only the key type should ever modify a key's payload.
1369 Furthermore, an RCU controlled payload must hold a struct rcu_head for the
1370 use of call_rcu() and, if the payload is of variable size, the length of
1371 the payload. key->datalen cannot be relied upon to be consistent with the
1372 payload just dereferenced if the key's semaphore is not held.
1374 Note that key->payload.data[0] has a shadow that is marked for __rcu
1375 usage. This is called key->payload.rcu_data0. The following accessors
1378 a) Set or change the first payload pointer::
1382 b) Read the first payload pointer with the key semaphore held::
1390 c) Read the first payload pointer with the RCU read lock held::
1416 This is optional - it supplies the default payload data length as
1417 contributed to the quota. If the key type's payload is always or almost
1438 This optional method permits the key type to attempt to parse payload
1444 union key_payload payload;
1452 the payload blob parameters; quotalen will be filled in with the default
1456 If a description can be proposed from the payload contents, that should be
1460 The method can attach anything it likes to payload. This is merely passed
1472 and payload fields of the key_preparsed_payload struct as filled in by the
1479 This method is called to attach a payload to a key during construction.
1480 The payload attached need not bear any relation to the data passed to this
1483 The prep->data and prep->datalen fields will define the original payload
1489 This method does not have to lock the key in order to attach a payload.
1496 prep->payload.data[] to key->payload.data[], with RCU-safe assignment on
1497 the first element. It will then clear prep->payload.data[] so that the
1504 It is called to update a key's payload from the blob of data provided.
1506 The prep->data and prep->datalen fields will define the original payload
1515 but this only deters other writers; any changes to the key's payload must
1517 the old payload.
1579 This method is optional. It is called to discard part of the payload
1589 This method is optional. It is called to discard the payload data on a key
1592 This method does not need to lock the key to access the payload; it can
1602 summarise a key's description and payload in text form.
1605 should be used to read the payload pointer if the payload is to be
1607 contents of the payload.
1618 key's payload into something a blob of data for userspace to deal with.
1626 prevent the key's payload changing. It is not necessary to use RCU locking
1627 when accessing the key's payload. It is safe to sleep in this method, such