From: Andrey Pronin <apronin@chromium.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Andrey Pronin <apronin@chromium.org>,
groeck@chromium.org, smbarber@chromium.org,
dianders@chromium.org
Subject: [PATCH 0/2] tpm: add optional max xfer size check
Date: Thu, 14 Jul 2016 18:39:03 -0700 [thread overview]
Message-ID: <1468546745-14646-1-git-send-email-apronin@chromium.org> (raw)
This patchset introduces an optional maximum transfer size that can
be specified by a tpm driver. Setting the max_xfer_size helps to catch
the cases when burstcnt is incorrectly reported by the device (e.g. >64
for spi - happened in practice) and gracefully handle such situations.
Andrey Pronin (2):
tpm_tis_core: add optional max xfer size check
tpm_tis_spi: add max xfer size
drivers/char/tpm/tpm_tis_core.c | 17 +++++++++++++++--
drivers/char/tpm/tpm_tis_core.h | 13 +++++++++++++
drivers/char/tpm/tpm_tis_spi.c | 1 +
3 files changed, 29 insertions(+), 2 deletions(-)
--
2.6.6
next reply other threads:[~2016-07-15 1:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 1:39 Andrey Pronin [this message]
2016-07-15 1:39 ` [PATCH 1/2] tpm_tis_core: add optional max xfer size check Andrey Pronin
2016-07-15 3:13 ` Jason Gunthorpe
2016-07-15 3:25 ` Andrey Pronin
2016-07-15 3:48 ` Guenter Roeck
2016-07-18 18:53 ` Jarkko Sakkinen
2016-07-15 1:39 ` [PATCH 2/2] tpm_tis_spi: add max xfer size Andrey Pronin
2016-07-20 2:34 ` [PATCH v2 0/2] tpm: add optional max xfer size check Andrey Pronin
2016-07-20 2:34 ` [PATCH v2 1/2] tpm_tis_core: " Andrey Pronin
2016-07-20 2:34 ` [PATCH v2 2/2] tpm_tis_spi: add max xfer size Andrey Pronin
2016-07-20 15:10 ` [PATCH v2 0/2] tpm: add optional max xfer size check Jarkko Sakkinen
2016-07-28 3:49 ` [PATCH v3 " Andrey Pronin
2016-07-28 3:49 ` [PATCH v3 1/2] tpm_tis_core: " Andrey Pronin
2016-07-28 22:52 ` Dmitry Torokhov
2016-08-09 8:14 ` Jarkko Sakkinen
2016-07-28 3:49 ` [PATCH v3 2/2] tpm_tis_spi: add max xfer size Andrey Pronin
2016-07-28 22:53 ` Dmitry Torokhov
2016-08-09 8:14 ` 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=1468546745-14646-1-git-send-email-apronin@chromium.org \
--to=apronin@chromium.org \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=smbarber@chromium.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
/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).