You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

David Howells 34574dd10b keys: Handle there being no fallback destination keyring for request_key() ... When request_key() is called, without there being any standard process keyrings on which to fall back if a destination keyring is not specified, an oops is liable to occur when construct_alloc_key() calls down_write() on dest_keyring's semaphore. Due to function inlining this may be seen as an oops in down_write() as called from request_key_and_link(). This situation crops up during boot, where request_key() is called from within the kernel (such as in CIFS mounts) where nobody is actually logged in, and so PAM has not had a chance to create a session keyring and user keyrings to act as the fallback. To fix this, make construct_alloc_key() not attempt to cache a key if there is no fallback key if no destination keyring is given specifically. Signed-off-by: David Howells <dhowells@redhat.com> Tested-by: Jeff Layton <jlayton@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		16 years ago
..
integrity/ima	…
keys	keys: Handle there being no fallback destination keyring for request_key()	16 years ago
selinux	…
smack	…
tomoyo	tomoyo: remove "undelete domain" command.	16 years ago
Kconfig	…
Makefile	…
capability.c	…
commoncap.c	cap_prctl: don't set error to 0 at 'no_change'	16 years ago
device_cgroup.c	…
inode.c	…
root_plug.c	…
security.c	…