From: Srish Srinivasan <ssrish@linux.ibm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-integrity@vger.kernel.org, keyrings@vger.kernel.org,
James.Bottomley@hansenpartnership.com, zohar@linux.ibm.com,
stefanb@linux.ibm.com, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, nayna@linux.ibm.com,
rnsastry@linux.ibm.com
Subject: Re: [PATCH] keys/trusted_keys: reuse TPM version in option handling
Date: Fri, 2 Oct 2026 12:29:41 +0530 [thread overview]
Message-ID: <2c71655a-53c7-4e63-9e38-7372fae74a0e@linux.ibm.com> (raw)
In-Reply-To: <ar8ln4Au8rDe_Ssm@kernel.org>
Hi Jarkko,
Thanks for taking a look.
On 10/2/26 9:01 AM, Jarkko Sakkinen wrote:
> On Wed, Sep 30, 2026 at 11:32:17AM +0530, Srish Srinivasan wrote:
>> Determine the TPM version once in the seal and unseal paths and reuse it
>> when allocating and parsing trusted key options. This avoids redundant TPM
>> version checks.
>>
>> Signed-off-by: Srish Srinivasan <ssrish@linux.ibm.com>
>> Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>
>> ---
>> security/keys/trusted-keys/trusted_tpm1.c | 22 ++++++----------------
>> 1 file changed, 6 insertions(+), 16 deletions(-)
>>
>> diff --git a/security/keys/trusted-keys/trusted_tpm1.c b/security/keys/trusted-keys/trusted_tpm1.c
>> index 3ec078ca3f97..70de4101923f 100644
>> --- a/security/keys/trusted-keys/trusted_tpm1.c
>> +++ b/security/keys/trusted-keys/trusted_tpm1.c
>> @@ -700,7 +700,7 @@ static const match_table_t key_tokens = {
>>
>> /* can have zero or more token= options */
>> static int getoptions(char *c, struct trusted_key_payload *pay,
>> - struct trusted_key_options *opt)
>> + struct trusted_key_options *opt, int tpm2)
>> {
>> struct trusted_key_tpm *private = opt->private;
>> substring_t args[MAX_OPT_ARGS];
>> @@ -712,11 +712,6 @@ static int getoptions(char *c, struct trusted_key_payload *pay,
>> unsigned long token_mask = 0;
>> unsigned int digest_len;
>> int i;
>> - int tpm2;
>> -
>> - tpm2 = tpm_is_tpm2(chip);
>> - if (tpm2 < 0)
>> - return tpm2;
>>
>> private->hash = tpm2 ? HASH_ALGO_SHA256 : HASH_ALGO_SHA1;
>>
>> @@ -838,15 +833,10 @@ static int getoptions(char *c, struct trusted_key_payload *pay,
>> return 0;
>> }
>>
>> -static struct trusted_key_options *trusted_options_alloc(void)
>> +static struct trusted_key_options *trusted_options_alloc(int tpm2)
> Probably "bool is_tpm2" would be better here. It does not need to be
> tightly coupled with the tristate acquired from tpm_is_tpm2.
Makes sense.
Sure, I will make this change and send out v2.
>
>> {
>> struct trusted_key_tpm *private;
>> struct trusted_key_options *options;
>> - int tpm2;
>> -
>> - tpm2 = tpm_is_tpm2(chip);
>> - if (tpm2 < 0)
>> - return NULL;
>>
>> options = kzalloc_obj(*options);
>> if (options) {
>> @@ -877,13 +867,13 @@ static int trusted_tpm_seal(struct trusted_key_payload *p, char *datablob)
>> if (tpm2 < 0)
>> return tpm2;
>>
>> - options = trusted_options_alloc();
>> + options = trusted_options_alloc(tpm2);
>> if (!options)
>> return -ENOMEM;
>>
>> private = options->private;
>>
>> - ret = getoptions(datablob, p, options);
>> + ret = getoptions(datablob, p, options, tpm2);
>> if (ret < 0)
>> return ret;
>> dump_options(options);
>> @@ -922,12 +912,12 @@ static int trusted_tpm_unseal(struct trusted_key_payload *p, char *datablob)
>> if (tpm2 < 0)
>> return tpm2;
>>
>> - options = trusted_options_alloc();
>> + options = trusted_options_alloc(tpm2);
>> if (!options)
>> return -ENOMEM;
>> private = options->private;
>>
>> - ret = getoptions(datablob, p, options);
>> + ret = getoptions(datablob, p, options, tpm2);
>> if (ret < 0)
>> return ret;
>> dump_options(options);
>> --
>> 2.53.0
>>
> Br, Jarkko
Thanks,
Srish.
prev parent reply other threads:[~2026-10-02 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 6:02 Srish Srinivasan
2026-10-02 3:31 ` Jarkko Sakkinen
2026-10-02 6:59 ` Srish Srinivasan [this message]
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=2c71655a-53c7-4e63-9e38-7372fae74a0e@linux.ibm.com \
--to=ssrish@linux.ibm.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jarkko@kernel.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=nayna@linux.ibm.com \
--cc=rnsastry@linux.ibm.com \
--cc=stefanb@linux.ibm.com \
--cc=zohar@linux.ibm.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
all inboxes | Powered by JetHome®