From: Jarkko Sakkinen <jarkko@kernel.org>
To: linux-integrity@vger.kernel.org
Cc: dpsmith@apertussolutions.com, ross.philipson@oracle.com,
Jarkko Sakkinen <jarkko@kernel.org>,
David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org (open list:KEYS/KEYRINGS),
linux-security-module@vger.kernel.org (open list:SECURITY
SUBSYSTEM), linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v2 0/9] tpm: Decouple PCR extend from driver
Date: Mon, 29 Sep 2025 06:59:29 +0300 [thread overview]
Message-ID: <20250929035938.1773341-1-jarkko@kernel.org> (raw)
Decouple tpm2-sessions enough from implementation so that building for PCR
extend commands can be decoupled from rest of the implementation. This is
a mandatory for Trenchboot series, and including all these changes for
that series would over-complicate it.
This is first part of refactorizations for make grounds for Trenchboot,
and still aimed for 6.18. The second part includes robustness updates
for tpm-buf.
v2:
- While including fixes from v1, this patch set has a refocus in order to
do minimal changes to make code base more compatible Trenchboot.
Jarkko Sakkinen (9):
tpm: cap PCR bank in tpm2_get_pcr_allocations()
tpm: Use -EPERM as fallback error code in tpm_ret_to_err
KEYS: trusted: Use tpm_ret_to_err() in trusted_tpm2
tpm2-sessions: Remove 'attributes' from tpm_buf_append_auth
tpm2-sessions: Umask tpm_buf_append_hmac_session()
KEYS: trusted: Open code tpm2_buf_append()
tpm-buf: check for corruption in tpm_buf_append_handle()
tpm-buf: Remove chip parameeter from tpm_buf_append_handle
tpm-buf: Build PCR extend commands
drivers/char/tpm/tpm-buf.c | 85 +++++++++++++++++---
drivers/char/tpm/tpm-chip.c | 13 +++-
drivers/char/tpm/tpm.h | 1 -
drivers/char/tpm/tpm1-cmd.c | 40 ++--------
drivers/char/tpm/tpm2-cmd.c | 39 ++++++----
drivers/char/tpm/tpm2-sessions.c | 7 +-
include/linux/tpm.h | 61 +++++----------
include/linux/tpm_command.h | 5 +-
security/keys/trusted-keys/trusted_tpm2.c | 95 +++++++----------------
9 files changed, 170 insertions(+), 176 deletions(-)
--
2.39.5
next reply other threads:[~2025-09-29 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 3:59 Jarkko Sakkinen [this message]
2025-09-29 3:59 ` [PATCH v2 1/9] tpm: cap PCR bank in tpm2_get_pcr_allocations() Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 2/9] tpm: Use -EPERM as fallback error code in tpm_ret_to_err Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 3/9] KEYS: trusted: Use tpm_ret_to_err() in trusted_tpm2 Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 4/9] tpm2-sessions: Remove 'attributes' from tpm_buf_append_auth Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 5/9] tpm2-sessions: Umask tpm_buf_append_hmac_session() Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 6/9] KEYS: trusted: Open code tpm2_buf_append() Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 7/9] tpm-buf: check for corruption in tpm_buf_append_handle() Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 8/9] tpm-buf: Remove chip parameeter from tpm_buf_append_handle Jarkko Sakkinen
2025-09-29 3:59 ` [PATCH v2 9/9] tpm-buf: Build PCR extend commands 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=20250929035938.1773341-1-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=dpsmith@apertussolutions.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=ross.philipson@oracle.com \
--cc=serge@hallyn.com \
/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).