From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jonathan McDowell <noodles@earth.li>
Cc: rust-for-linux@vger.kernel.org, linux-integrity@vger.kernel.org
Subject: Re: Using Rust on non-Rust side of kernel
Date: Tue, 26 Aug 2025 11:56:43 +0300 [thread overview]
Message-ID: <aK12y2NuBmA4SfyM@kernel.org> (raw)
In-Reply-To: <aK1xvMTqoq-6JyHm@earth.li>
On Tue, Aug 26, 2025 at 09:35:08AM +0100, Jonathan McDowell wrote:
> d4640c394f23 tpm: Check for completion after timeout
> 2f661f71fda1 tpm: tis: Double the timeout B to 4s
> 1dbf74e00a5f tpm: End any active auth session before shutdown
> de9e33df7762 tpm, tpm_tis: Workaround failed command reception on Infineon devices
> 7146dffa875c tpm, tpm_tis: Fix timeout handling when waiting for TPM status
> e3aaebcbb7c6 tpm: Clean up TPM space after command failure
I think we're in the same line here really :-) And apologies for
over-reacting, I definitely went over the top!
I did the marshaller/unmarshaller exactly for Rust TPM driver only in
the sense that if I got a patch set on my table doing that, it would be
the part which is complex enough that I would actually be in trouble.
So consider it like "years ahead preparation".
I quickly went through your list as a reality check if I have blind
spot but for the most part it is "business as usual" type of stuff,
some to change done many years ago (at least as old as tpmrm0).
Obvious exception to the rule are bugs related to HMAC encryption
to which I think we have now a resolution.
BR, Jarkko
next prev parent reply other threads:[~2025-08-26 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 12:12 Using Rust on non-Rust side of kernel Jarkko Sakkinen
2025-08-23 12:22 ` Jarkko Sakkinen
[not found] ` <BE42A51A-60C4-4E79-8459-CADEAB8DC3BA@collabora.com>
2025-08-23 23:06 ` Jarkko Sakkinen
2025-08-23 23:12 ` Jarkko Sakkinen
2025-08-24 1:12 ` Daniel Almeida
2025-08-24 7:15 ` Jarkko Sakkinen
2025-08-24 9:21 ` Jarkko Sakkinen
2025-08-23 23:41 ` Jarkko Sakkinen
2025-08-23 23:50 ` Jarkko Sakkinen
2025-08-25 12:04 ` Jonathan McDowell
2025-08-25 19:30 ` Jarkko Sakkinen
2025-08-25 19:42 ` Jarkko Sakkinen
2025-08-25 22:29 ` Jarkko Sakkinen
2025-08-25 23:23 ` Jarkko Sakkinen
2025-08-26 8:35 ` Jonathan McDowell
2025-08-26 8:56 ` Jarkko Sakkinen [this message]
2025-08-26 9:13 ` 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=aK12y2NuBmA4SfyM@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=noodles@earth.li \
--cc=rust-for-linux@vger.kernel.org \
/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).