KEYS: Fix some sparse warnings

Fix some sparse warnings in the keyrings code:

 (1) compat_keyctl_instantiate_key_iov() should be static.

 (2) There were a couple of places where a pointer was being compared against
     integer 0 rather than NULL.

 (3) keyctl_instantiate_key_common() should not take a __user-labelled iovec
     pointer as the caller must have copied the iovec to kernel space.

 (4) __key_link_begin() takes and __key_link_end() releases
     keyring_serialise_link_sem under some circumstances and so this should be
     declared.

     Note that adding __acquires() and __releases() for this doesn't help cure
     the warnings messages - something only commenting out both helps.

Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: James Morris <james.l.morris@oracle.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/security/keys/compat.c b/security/keys/compat.c
index fab4f8dda6c6..e35ae1d208a8 100644
--- a/security/keys/compat.c
+++ b/security/keys/compat.c
@@ -24,7 +24,7 @@
  *
  * If successful, 0 will be returned.
  */
-long compat_keyctl_instantiate_key_iov(
+static long compat_keyctl_instantiate_key_iov(
         key_serial_t id,
         const struct compat_iovec __user *_payload_iov,
         unsigned ioc,
@@ -33,7 +33,7 @@ long compat_keyctl_instantiate_key_iov(
         struct iovec iovstack[UIO_FASTIOV], *iov = iovstack;
         long ret;
 
-        if (_payload_iov == 0 || ioc == 0)
+        if (!_payload_iov || !ioc)
                 goto no_payload;
 
         ret = compat_rw_copy_check_uvector(WRITE, _payload_iov, ioc,