From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Josh Zimmerman <joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH v3] tpm_tis: Check return values from get_burstcount.
Date: Thu, 27 Oct 2016 16:48:54 +0300 [thread overview]
Message-ID: <20161027134854.iaehtdgppnxqttv2@intel.com> (raw)
In-Reply-To: <20161026163341.GA19855-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
On Wed, Oct 26, 2016 at 09:33:41AM -0700, Josh Zimmerman wrote:
> If the TPM we're connecting to uses a static burst count, it will report
> a burst count of zero throughout the response read. However, get_burstcount
> assumes that a response of zero indicates that the TPM is not ready to
> receive more data. In this case, it returns a negative error code, which
> is passed on to tpm_tis_{write,read}_bytes as a u16, causing
> them to read/write far too many bytes.
>
> This patch checks for negative return codes and bails out from recv_data
> and tpm_tis_send_data.
>
> Fixes: 1107d065fdf1
Fixes line is missing the short summary.
/Jarkko
> Signed-off-by: Josh Zimmerman <joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
>
> ---
> Changelog v3:
> - Add signed-off-by.
> Changelog v2:
> - Fix typo (rc->burstcnt)
>
> ---
> drivers/char/tpm/tpm_tis_core.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c
> index e3bf31b..aed92b3 100644
> --- a/drivers/char/tpm/tpm_tis_core.c
> +++ b/drivers/char/tpm/tpm_tis_core.c
> @@ -186,6 +186,12 @@ static int recv_data(struct tpm_chip *chip, u8 *buf, size_t count)
> chip->timeout_c,
> &priv->read_queue, true) == 0) {
> burstcnt = min_t(int, get_burstcount(chip), count - size);
> + if (burstcnt < 0) {
> + dev_err(&chip->dev,
> + "Unable to read burstcount in %s:%d (%s)\n",
> + __FILE__, __LINE__, __func__);
> + return burstcnt;
> + }
I gave this even more thought. This should be just
dev_err(&chip->dev, "Unable to read burstcount\n");
Use ftrace if you want to know the call site.
/Jarkko
>
> rc = tpm_tis_read_bytes(priv, TPM_DATA_FIFO(priv->locality),
> burstcnt, buf + size);
> @@ -272,6 +278,13 @@ static int tpm_tis_send_data(struct tpm_chip *chip, u8 *buf, size_t len)
>
> while (count < len - 1) {
> burstcnt = min_t(int, get_burstcount(chip), len - count - 1);
> + if (burstcnt < 0) {
> + dev_err(&chip->dev,
> + "Unable to read burstcount in %s:%d (%s)\n",
> + __FILE__, __LINE__, __func__);
> + rc = burstcnt;
> + goto out_err;
> + }
> rc = tpm_tis_write_bytes(priv, TPM_DATA_FIFO(priv->locality),
> burstcnt, buf + count);
> if (rc < 0)
> --
> 2.8.0.rc3.226.g39d4020
>
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
prev parent reply other threads:[~2016-10-27 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 16:33 [PATCH v3] tpm_tis: Check return values from get_burstcount Josh Zimmerman
[not found] ` <20161026163341.GA19855-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-10-27 13:48 ` Jarkko Sakkinen [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=20161027134854.iaehtdgppnxqttv2@intel.com \
--to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=joshz-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).