linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
	linux-integrity@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: kselftest and cargo
Date: Thu, 18 Sep 2025 18:06:27 +0300	[thread overview]
Message-ID: <aMwf89qekCuAdD1L@kernel.org> (raw)
In-Reply-To: <f18854b2-f9c8-44a3-a09d-3b2ddbcb971a@linuxfoundation.org>

On Tue, Sep 16, 2025 at 04:39:37PM -0600, Shuah Khan wrote:
> On 9/16/25 07:48, Jarkko Sakkinen wrote:
> > Hi,
> > 
> > The pre-existing kselftest for TPM2 is derived works of my earlier Python
> > based rudimentary TPM2 stack called 'tpm2-scripts'.
> > 
> > In order to get more coverage and more mainintainable and extensible test
> > suite I'd like to eventually rewrite the tests with bash and tpm2sh, which
> > is a TPM2 cli written with Rust and based on my new TPM2 stack [1] [2].
> > 
> > Given linux-rust work, would it be acceptable to require cargo to install
> > a runner for kselftest? I'm finishing off now 0.11 version of the tool,
> > which will take some time (versions before that are honestly quite bad,
> > don't try them) but after that this would be something I'd like to
> > put together.
> 
> Probably fine - how does this impact kselftest default run?

OK so this was early query: I might introduce such test as part
of series that hasa waited for long time for an update [1]. I can
use tpm2sh more easily to reproduce equivalent crypto as kernel
does and make a test that can compare the results in a meaningful
manner. I also plan to relocate tpm2sh as part of git.kernel.org
custody from Github, as its main dependency tpm2-protocol crate 
already is [2].

I went over the top in the original mail: most definitely it makes
sense to retain the pre-existing test, and such "Rust-enhanced"
test should be conditional, and can instead of depending on cargo
simply do "command -v" in order to check the existence of tpm2sh
and output installation instructions if it is missing.

With those precautions it should be somewhat harmless unless you
actually want to run that test.

Thanks for quick response!

[1] https://lore.kernel.org/linux-integrity/20240528210823.28798-1-jarkko@kernel.org/
[2] https://git.kernel.org/pub/scm/linux/kernel/git/jarkko/tpm2-protocol.git

BR, Jarkko

  reply	other threads:[~2025-09-18 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16 13:48 kselftest and cargo Jarkko Sakkinen
2025-09-16 13:52 ` Jarkko Sakkinen
2025-09-16 22:39 ` Shuah Khan
2025-09-18 15:06   ` Jarkko Sakkinen [this message]
2025-09-18 15:15     ` Jarkko Sakkinen
2025-09-18 16:04       ` Shuah Khan
2025-09-18 16:35         ` 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=aMwf89qekCuAdD1L@kernel.org \
    --to=jarkko@kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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).