public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 v4 0/4] Optimize tpm2_read_public() calls
Date: Fri,  5 Dec 2025 17:19:49 +0200	[thread overview]
Message-ID: <20251205151955.298182-1-jarkko@kernel.org> (raw)

The main goal is fairly straight-forwrd here.

The aim of these patches is optimize the number of tpm2_read_public()
calls to the bare minimum. The last patch is a bit out of scope but
I included because it builds on top of this work.

Jarkko Sakkinen (4):
  KEYS: trusted: Re-orchestrate tpm2_read_public() calls
  KEYS: trusted: Store parent's name to the encoded keys
  KEYS: trusted: Open code tpm2_buf_append()
  tpm2-sessions: Enforce single authorized handle

 drivers/char/tpm/tpm2-cmd.c               |  93 +++++++-
 drivers/char/tpm/tpm2-sessions.c          | 169 ++-------------
 include/linux/tpm.h                       |   3 +-
 security/keys/trusted-keys/tpm2key.asn1   |  17 +-
 security/keys/trusted-keys/trusted_tpm2.c | 250 +++++++++++++---------
 5 files changed, 272 insertions(+), 260 deletions(-)

-- 
2.52.0


             reply	other threads:[~2025-12-05 15:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 15:19 Jarkko Sakkinen [this message]
2025-12-05 15:19 ` [PATCH v4 1/4] KEYS: trusted: Re-orchestrate tpm2_read_public() calls Jarkko Sakkinen
2025-12-05 15:19 ` [PATCH v4 2/4] KEYS: trusted: Store parent's name to the encoded keys Jarkko Sakkinen
2025-12-05 15:19 ` [PATCH v4 3/4] KEYS: trusted: Open code tpm2_buf_append() Jarkko Sakkinen
2025-12-05 15:19 ` [PATCH v4 4/4] tpm2-sessions: Enforce single authorized handle 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=20251205151955.298182-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox