From: nayna@linux.vnet.ibm.com (Nayna Jain)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 2/3] keys: export find_keyring_by_name()
Date: Wed, 28 Feb 2018 23:25:20 +0530 [thread overview]
Message-ID: <20180228175521.10287-2-nayna@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180228175521.10287-1-nayna@linux.vnet.ibm.com>
This patch exports the function find_keyring_by_name()
to be used by other subsystems.
Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com>
---
include/linux/key.h | 2 ++
security/keys/internal.h | 2 --
security/keys/keyring.c | 1 +
3 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/include/linux/key.h b/include/linux/key.h
index e58ee10f6e58..c8d332d4103c 100644
--- a/include/linux/key.h
+++ b/include/linux/key.h
@@ -346,6 +346,8 @@ static inline key_serial_t key_serial(const struct key *key)
extern void key_set_timeout(struct key *, unsigned);
+extern struct key *find_keyring_by_name(const char *name, bool uid_keyring);
+
/*
* The permissions required on a key that we're looking up.
*/
diff --git a/security/keys/internal.h b/security/keys/internal.h
index 9f8208dc0e55..8aa8d347a1ab 100644
--- a/security/keys/internal.h
+++ b/security/keys/internal.h
@@ -141,8 +141,6 @@ extern key_ref_t keyring_search_aux(key_ref_t keyring_ref,
extern key_ref_t search_my_process_keyrings(struct keyring_search_context *ctx);
extern key_ref_t search_process_keyrings(struct keyring_search_context *ctx);
-extern struct key *find_keyring_by_name(const char *name, bool uid_keyring);
-
extern int install_user_keyrings(void);
extern int install_thread_keyring_to_cred(struct cred *);
extern int install_process_keyring_to_cred(struct cred *);
diff --git a/security/keys/keyring.c b/security/keys/keyring.c
index d0bccebbd3b5..0fd230534685 100644
--- a/security/keys/keyring.c
+++ b/security/keys/keyring.c
@@ -1159,6 +1159,7 @@ struct key *find_keyring_by_name(const char *name, bool uid_keyring)
read_unlock(&keyring_name_lock);
return keyring;
}
+EXPORT_SYMBOL(find_keyring_by_name);
static int keyring_detect_cycle_iterator(const void *object,
void *iterator_data)
--
2.13.6
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-02-28 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 17:55 [PATCH 1/3] certs: define a trusted platform keyring Nayna Jain
2018-02-28 17:55 ` Nayna Jain [this message]
2018-02-28 17:55 ` [PATCH 3/3] ima: support platform keyring for kernel appraisal Nayna Jain
2018-03-07 16:03 ` [PATCH 1/3] certs: define a trusted platform keyring David Howells
2018-03-07 17:47 ` Nayna Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180228175521.10287-2-nayna@linux.vnet.ibm.com \
--to=nayna@linux.vnet.ibm.com \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).