From: Keith Busch <kbusch@kernel.org>
To: Hannes Reinecke <hare@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 3/9] nvme-tcp: check for invalidated or revoked key
Date: Mon, 29 Jul 2024 08:43:52 -0600 [thread overview]
Message-ID: <ZqeqqK3XBk_eoyZb@kbusch-mbp> (raw)
In-Reply-To: <20240722120226.88737-4-hare@kernel.org>
On Mon, Jul 22, 2024 at 02:02:20PM +0200, Hannes Reinecke wrote:
> diff --git a/drivers/nvme/common/keyring.c b/drivers/nvme/common/keyring.c
> index 05e89307c8aa..ed5167f942d8 100644
> --- a/drivers/nvme/common/keyring.c
> +++ b/drivers/nvme/common/keyring.c
> @@ -20,6 +20,28 @@ key_serial_t nvme_keyring_id(void)
> }
> EXPORT_SYMBOL_GPL(nvme_keyring_id);
>
> +static bool nvme_tls_psk_revoked(struct key *psk)
> +{
> + return test_bit(KEY_FLAG_REVOKED, &psk->flags) ||
> + test_bit(KEY_FLAG_INVALIDATED, &psk->flags);
> +}
> +
> +struct key *nvme_tls_key_lookup(key_serial_t key_id)
> +{
> + struct key *key = key_lookup(key_id);
> +
> + if (IS_ERR(key)) {
> + pr_err("key id %08x not found\n", key_id);
> + return key;
> + }
> + if (nvme_tls_psk_revoked(key)) {
> + pr_err("key id %08x revoked\n", key_id);
> + return ERR_PTR(-EKEYREVOKED);
> + }
> + return key;
> +}
> +EXPORT_SYMBOL_GPL(nvme_tls_key_lookup);
> +
> static void nvme_tls_psk_describe(const struct key *key, struct seq_file *m)
> {
> seq_puts(m, key->description);
> diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
> index f5f545fa0103..432efcbf9e2f 100644
> --- a/drivers/nvme/host/fabrics.c
> +++ b/drivers/nvme/host/fabrics.c
> @@ -665,7 +665,7 @@ static struct key *nvmf_parse_key(int key_id)
> return ERR_PTR(-EINVAL);
> }
>
> - key = key_lookup(key_id);
> + key = nvme_tls_key_lookup(key_id);
We've had some fallout before with nvme modules vs built-in, so I test
for this now. Here's the relevant parts of my config:
CONFIG_NVME_KEYRING=m
...
CONFIG_NVME_FABRICS=y
...
CONFIG_NVME_TCP=m
And that gets this error:
vmlinux.o: in function `nvmf_parse_key':
/home/kbusch/src/linux/drivers/nvme/host/fabrics.c:668: undefined reference to `nvme_tls_key_lookup'
next prev parent reply other threads:[~2024-07-29 14:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 12:02 [PATCHv8 0/9] nvme: fixes for secure concatenation Hannes Reinecke
2024-07-22 12:02 ` [PATCH 1/9] nvme-keyring: restrict match length for version '1' identifiers Hannes Reinecke
2024-07-23 14:43 ` Christoph Hellwig
2024-07-22 12:02 ` [PATCH 2/9] nvme-tcp: sanitize TLS key handling Hannes Reinecke
2024-07-22 12:02 ` [PATCH 3/9] nvme-tcp: check for invalidated or revoked key Hannes Reinecke
2024-07-23 14:43 ` Christoph Hellwig
2024-07-29 14:43 ` Keith Busch [this message]
2024-07-31 9:45 ` Sagi Grimberg
2024-08-12 6:25 ` Hannes Reinecke
2024-08-12 14:09 ` Hannes Reinecke
2024-08-12 15:17 ` Keith Busch
2024-08-13 19:29 ` Sagi Grimberg
2024-07-22 12:02 ` [PATCH 4/9] nvme: add a newline to the 'tls_key' sysfs attribute Hannes Reinecke
2024-07-22 12:02 ` [PATCH 5/9] nvme: split off TLS sysfs attributes into a separate group Hannes Reinecke
2024-07-23 14:49 ` Christoph Hellwig
2024-07-23 17:29 ` Hannes Reinecke
2024-07-23 18:17 ` Sagi Grimberg
2024-07-24 13:41 ` Christoph Hellwig
2024-07-22 12:02 ` [PATCH 6/9] nvme-sysfs: add 'tls_configured_key' sysfs attribute Hannes Reinecke
2024-07-22 12:02 ` [PATCH 7/9] nvme-sysfs: add 'tls_keyring' attribute Hannes Reinecke
2024-07-22 12:02 ` [PATCH 8/9] nvmet-auth: allow to clear DH-HMAC-CHAP keys Hannes Reinecke
2024-07-22 12:02 ` [PATCH 9/9] nvme-target: do not check authentication status for admin commands twice Hannes Reinecke
2024-07-28 20:50 ` [PATCHv8 0/9] nvme: fixes for secure concatenation Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 8:38 [PATCHv7 " Hannes Reinecke
2024-07-19 8:38 ` [PATCH 3/9] nvme-tcp: check for invalidated or revoked key Hannes Reinecke
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=ZqeqqK3XBk_eoyZb@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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