From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>,
William Roberts <bill.c.roberts@gmail.com>,
David Howells <dhowells@redhat.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Mimi Zohar <zohar@linux.ibm.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Jerry Snitselaar <jsnitsel@redhat.com>
Subject: Re: [PATCH v6 7/8] tpm: Add tpm_buf_read_{u8,u16,u32}
Date: Tue, 28 Nov 2023 07:35:15 -0500 [thread overview]
Message-ID: <dd74fdb8-93af-4799-b23a-b2595acfc8aa@linux.ibm.com> (raw)
In-Reply-To: <20231124020237.27116-8-jarkko@kernel.org>
On 11/23/23 21:02, Jarkko Sakkinen wrote:
> Declare reader functions for the instances of struct tpm_buf. If the read
> goes out of boundary, TPM_BUF_BOUNDARY_ERROR is set, and subsequent read
> will do nothing.
>
> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
> ---
> + */
> +u16 tpm_buf_read_u16(struct tpm_buf *buf, off_t *offset)
> +{
> + u16 value;
This should be __be16 ...
> +
> + tpm_buf_read(buf, offset, sizeof(value), &value);
> +
> + return be16_to_cpu(value);
> +}
> +EXPORT_SYMBOL_GPL(tpm_buf_read_u16);
> +
> +/**
> + * tpm_buf_read_u32() - Read 32-bit word from a TPM buffer
> + * @buf: &tpm_buf instance
> + * @offset: offset within the buffer
> + *
> + * Return: next 32-bit word
> + */
> +u32 tpm_buf_read_u32(struct tpm_buf *buf, off_t *offset)
> +{
> + u32 value;
... and this __be32 to avoid this here:
drivers/char/tpm/tpm-buf.c:203:16: warning: cast to restricted __be16
drivers/char/tpm/tpm-buf.c:220:16: warning: cast to restricted __be32
next prev parent reply other threads:[~2023-11-28 12:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 2:02 [PATCH v6 0/8] Extend struct tpm_buf to support sized buffers (TPM2B) Jarkko Sakkinen
2023-11-24 2:02 ` [PATCH v6 1/8] tpm: Remove unused tpm_buf_tag() Jarkko Sakkinen
2023-11-27 20:33 ` Stefan Berger
2023-11-24 2:02 ` [PATCH v6 2/8] tpm: Remove tpm_send() Jarkko Sakkinen
2023-11-27 20:37 ` Stefan Berger
2023-11-24 2:02 ` [PATCH v6 3/8] tpm: Move buffer handling from static inlines to real functions Jarkko Sakkinen
2023-11-27 20:40 ` Stefan Berger
2023-11-24 2:02 ` [PATCH v6 4/8] tpm: Update struct tpm_buf documentation comments Jarkko Sakkinen
2023-11-27 20:41 ` Stefan Berger
2023-12-04 2:40 ` Jarkko Sakkinen
2023-11-24 2:02 ` [PATCH v6 5/8] tpm: Store the length of the tpm_buf data separately Jarkko Sakkinen
2023-11-27 21:03 ` Stefan Berger
2023-11-24 2:02 ` [PATCH v6 6/8] tpm: TPM2B formatted buffers Jarkko Sakkinen
2023-11-27 21:08 ` Stefan Berger
2023-11-24 2:02 ` [PATCH v6 7/8] tpm: Add tpm_buf_read_{u8,u16,u32} Jarkko Sakkinen
2023-11-27 21:10 ` Stefan Berger
2023-11-28 12:35 ` Stefan Berger [this message]
2023-11-24 2:02 ` [PATCH v6 8/8] KEYS: trusted: tpm2: Use struct tpm_buf for sized buffers Jarkko Sakkinen
2023-11-27 21:21 ` Stefan Berger
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=dd74fdb8-93af-4799-b23a-b2595acfc8aa@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bill.c.roberts@gmail.com \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.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