From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
Peter Huewe <peterhuewe@gmx.de>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Naveen N Rao <naveen@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-integrity@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sumit Garg <sumit.garg@kernel.org>,
linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH v3 2/4] tpm: support devices with synchronous send()
Date: Wed, 30 Apr 2025 18:41:43 +0300 [thread overview]
Message-ID: <aBJEt41g_T7Thm6s@kernel.org> (raw)
In-Reply-To: <20250414145653.239081-3-sgarzare@redhat.com>
On Mon, Apr 14, 2025 at 04:56:51PM +0200, Stefano Garzarella wrote:
> From: Stefano Garzarella <sgarzare@redhat.com>
>
> Some devices do not support interrupts and provide a single synchronous
> operation to send the command and receive the response on the same buffer.
>
> Currently, these types of drivers must use an internal buffer where they
> temporarily store the response between .send() and recv() calls.
>
> Introduce a new flag (TPM_CHIP_FLAG_SYNC) to support synchronous send().
> If that flag is set by the driver, tpm_try_transmit() will use the send()
> callback to send the command and receive the response on the same buffer
> synchronously. In that case send() return the number of bytes of the
> response on success, or -errno on failure.
>
> Suggested-by: Jason Gunthorpe <jgg@ziepe.ca>
> Suggested-by: Jarkko Sakkinen <jarkko@kernel.org>
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> ---
> v3:
> - fixed comment style [Jarkko]
> - renamend `out_send_sync` label to `out_sync` [Jarkko]
> ---
> include/linux/tpm.h | 1 +
> drivers/char/tpm/tpm-interface.c | 20 +++++++++++++++++---
> 2 files changed, 18 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/tpm.h b/include/linux/tpm.h
> index 2e38edd5838c..0e9746dc9d30 100644
> --- a/include/linux/tpm.h
> +++ b/include/linux/tpm.h
> @@ -350,6 +350,7 @@ enum tpm_chip_flags {
> TPM_CHIP_FLAG_SUSPENDED = BIT(8),
> TPM_CHIP_FLAG_HWRNG_DISABLED = BIT(9),
> TPM_CHIP_FLAG_DISABLE = BIT(10),
> + TPM_CHIP_FLAG_SYNC = BIT(11),
> };
>
> #define to_tpm_chip(d) container_of(d, struct tpm_chip, dev)
> diff --git a/drivers/char/tpm/tpm-interface.c b/drivers/char/tpm/tpm-interface.c
> index 3b6ddcdb4051..3dc06836f932 100644
> --- a/drivers/char/tpm/tpm-interface.c
> +++ b/drivers/char/tpm/tpm-interface.c
> @@ -114,8 +114,19 @@ static ssize_t tpm_try_transmit(struct tpm_chip *chip, void *buf, size_t bufsiz)
> return rc;
> }
>
> - /* A sanity check. send() should just return zero on success e.g.
> - * not the command length.
> + /*
> + * Synchronous devices return the response directly during the send()
> + * call in the same buffer.
> + */
> + if (chip->flags & TPM_CHIP_FLAG_SYNC) {
> + len = rc;
> + rc = 0;
> + goto out_sync;
> + }
> +
> + /*
> + * A sanity check. send() of asynchronous devices should just return
> + * zero on success e.g. not the command length.
> */
> if (rc > 0) {
> dev_warn(&chip->dev,
> @@ -151,7 +162,10 @@ static ssize_t tpm_try_transmit(struct tpm_chip *chip, void *buf, size_t bufsiz)
> if (len < 0) {
> rc = len;
> dev_err(&chip->dev, "tpm_transmit: tpm_recv: error %d\n", rc);
> - } else if (len < TPM_HEADER_SIZE || len != be32_to_cpu(header->length))
> + return rc;
> + }
> +out_sync:
> + if (len < TPM_HEADER_SIZE || len != be32_to_cpu(header->length))
> rc = -EFAULT;
>
> return rc ? rc : len;
> --
> 2.49.0
>
I think this is ok.
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
next prev parent reply other threads:[~2025-04-30 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 14:56 [PATCH v3 0/4] tpm: add support for sync send() and use it in ftpm and svsm drivers Stefano Garzarella
2025-04-14 14:56 ` [PATCH v3 1/4] tpm: add buf_size parameter in the .send callback Stefano Garzarella
2025-04-30 15:39 ` Jarkko Sakkinen
2025-05-06 12:56 ` Stefano Garzarella
2025-05-08 20:00 ` Jarkko Sakkinen
2025-04-14 14:56 ` [PATCH v3 2/4] tpm: support devices with synchronous send() Stefano Garzarella
2025-04-30 15:41 ` Jarkko Sakkinen [this message]
2025-04-14 14:56 ` [PATCH v3 3/4] tpm/tpm_ftpm_tee: support TPM_CHIP_FLAG_SYNC Stefano Garzarella
2025-04-14 14:59 ` Stefano Garzarella
2025-04-28 7:49 ` Sumit Garg
2025-04-30 15:47 ` Jarkko Sakkinen
2025-05-06 13:03 ` Stefano Garzarella
2025-04-14 14:56 ` [PATCH v3 4/4] tpm/tpm_svsm: " Stefano Garzarella
2025-04-30 15:49 ` Jarkko Sakkinen
2025-05-06 13:06 ` Stefano Garzarella
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=aBJEt41g_T7Thm6s@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alexandre.belloni@bootlin.com \
--cc=christophe.leroy@csgroup.eu \
--cc=claudiu.beznea@tuxon.dev \
--cc=jens.wiklander@linaro.org \
--cc=jgg@ziepe.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=npiggin@gmail.com \
--cc=peterhuewe@gmx.de \
--cc=sgarzare@redhat.com \
--cc=sumit.garg@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).