From: Jarkko Sakkinen <jarkko@kernel.org>
To: linux-integrity@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 0/4] Streamline TPM2 HMAC sessions
Date: Tue, 9 Dec 2025 09:38:58 +0200 [thread overview]
Message-ID: <20251209073903.767518-1-jarkko@kernel.org> (raw)
Since we cannot at this point cache names of the keys given limitations
of the ASN.1 file format, I'll start a fresh patch set. Let's fixup what
we can right now.
This patch set addresses two major issues in the feature:
1. Dynamic resolution without gain. All kernel sites have at most single
handle to authorize. Even if this changes some day this is how it is
as of today and we definitely do not want to dictate the future but
instead downscale code to the metrics that we have as of today.
2. Eliminate at least one unnnecessary tpm2_read_public() call.
Jarkko Sakkinen (4):
tpm2-sessions: Define TPM2_NAME_MAX_SIZE
KEYS: trusted: Re-orchestrate tpm2_read_public() calls
tpm2-sessions: Remove AUTH_MAX_NAMES
tpm-buf: Remove tpm_buf_append_handle
drivers/char/tpm/tpm-buf.c | 25 -----
drivers/char/tpm/tpm2-cmd.c | 7 +-
drivers/char/tpm/tpm2-sessions.c | 120 +++++++--------------
include/linux/tpm.h | 20 +++-
security/keys/trusted-keys/trusted_tpm2.c | 126 ++++++++++++++--------
5 files changed, 138 insertions(+), 160 deletions(-)
--
2.52.0
next reply other threads:[~2025-12-09 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 7:38 Jarkko Sakkinen [this message]
2025-12-09 7:38 ` [PATCH 1/4] tpm2-sessions: Define TPM2_NAME_MAX_SIZE Jarkko Sakkinen
2025-12-09 7:39 ` [PATCH 2/4] KEYS: trusted: Re-orchestrate tpm2_read_public() calls Jarkko Sakkinen
2025-12-09 7:39 ` [PATCH 3/4] tpm2-sessions: Remove AUTH_MAX_NAMES Jarkko Sakkinen
2025-12-09 7:39 ` [PATCH 4/4] tpm-buf: Remove tpm_buf_append_handle Jarkko Sakkinen
2025-12-09 7:52 ` Jarkko Sakkinen
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=20251209073903.767518-1-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.