| Message ID | 20170309202315.15361-4-mathew.j.martineau@linux.intel.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
diff --git a/include/linux/key.h b/include/linux/key.h index c4016bc314f7..771eda3385e0 100644 --- a/include/linux/key.h +++ b/include/linux/key.h @@ -131,6 +131,13 @@ typedef int (*key_restrict_link_func_t)(struct key *dest_keyring, const union key_payload *payload, void *data); +struct key_restriction { + key_restrict_link_func_t check; + void (*free_data)(void *data); + void *data; + struct key_type *keytype; +}; + /*****************************************************************************/ /* * authentication token / access credential / keyring
Key link restrictions require restriction-specific data as well as a restriction-specific function pointer. As a first step toward replacing the restrict_link pointer in struct key, define a more general key_restriction structure that captures the function and data, as well as a data freeing function and a key type pointer for use in garbage collection. Key type modules should not be pinned on account of this key type pointer because the pointer will be cleared by the garbage collector if the key type is unregistered. Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com> --- include/linux/key.h | 7 +++++++ 1 file changed, 7 insertions(+)