From: Jarkko Sakkinen <jarkko@kernel.org>
To: linux-integrity@vger.kernel.org
Cc: Stefano Garzarella <sgarzare@redhat.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 v11 0/3] tpm: robust stack allocations
Date: Tue, 23 Sep 2025 20:07:41 +0300 [thread overview]
Message-ID: <20250923170744.1749132-1-jarkko@kernel.org> (raw)
1. These are previous changes to tpm_buf, which make stack allocations
much more feasible than previously.
2. Migrate low-hanging fruit to use stack allocations.
3. Re-orchestrate tpm_get_random().
Jarkko Sakkinen (3):
tpm: Make TPM buffer allocations more robust
tpm: Use TPM_MIN_BUF_SIZE in driver commands
tpm orchestrate tpm_get_random() in the function
drivers/char/tpm/tpm-buf.c | 139 +++++----
drivers/char/tpm/tpm-dev-common.c | 4 +-
drivers/char/tpm/tpm-dev.h | 2 +-
drivers/char/tpm/tpm-interface.c | 36 ++-
drivers/char/tpm/tpm-sysfs.c | 20 +-
drivers/char/tpm/tpm.h | 16 +-
drivers/char/tpm/tpm1-cmd.c | 177 +++++------
drivers/char/tpm/tpm2-cmd.c | 349 +++++++++-------------
drivers/char/tpm/tpm2-sessions.c | 127 ++++----
drivers/char/tpm/tpm2-space.c | 44 ++-
drivers/char/tpm/tpm_tis_i2c.c | 4 +-
drivers/char/tpm/tpm_vtpm_proxy.c | 34 +--
include/linux/tpm.h | 28 +-
security/keys/trusted-keys/trusted_tpm1.c | 34 +--
security/keys/trusted-keys/trusted_tpm2.c | 156 +++++-----
15 files changed, 556 insertions(+), 614 deletions(-)
--
2.39.5
next reply other threads:[~2025-09-23 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 17:07 Jarkko Sakkinen [this message]
2025-09-23 17:07 ` [PATCH v11 1/3] tpm: Make TPM buffer allocations more robust Jarkko Sakkinen
2025-09-23 17:07 ` [PATCH v11 2/3] tpm: Use TPM_MIN_BUF_SIZE in driver commands Jarkko Sakkinen
2025-09-23 17:07 ` [PATCH v11 3/3] tpm orchestrate tpm_get_random() in the function Jarkko Sakkinen
2025-09-24 1:31 ` [PATCH v11 0/3] tpm: robust stack allocations Jarkko Sakkinen
2025-09-24 1:37 ` 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=20250923170744.1749132-1-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.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=serge@hallyn.com \
--cc=sgarzare@redhat.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).