From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: jmorris@namei.org
Cc: linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: [GIT PULL] tpmdd fixes for 4.16
Date: Mon, 26 Feb 2018 14:41:44 +0200 [thread overview]
Message-ID: <20180226124144.GA8675@linux.intel.com> (raw)
Hi
Here is a batch of critical fixes for 4.16.
/Jarkko
The following changes since commit a02633e9b13dcb9b1a656b08f81bc8ba2d4d2294:
Merge tag 'v4.16-rc2' into next-general (2018-02-21 08:21:41 -0800)
are available in the Git repository at:
git://git.infradead.org/users/jjs/linux-tpmdd.git tags/tpmdd-next-20180226
for you to fetch changes up to 895fbcaba75da05f6337ffaf750778c3a8ee9158:
tpm_tis: fix potential buffer overruns caused by bit glitches on the bus (2018-02-26 14:33:57 +0200)
----------------------------------------------------------------
tpmdd fixes for Linux 4.16
----------------------------------------------------------------
Jeremy Boone (5):
tpm: fix potential buffer overruns caused by bit glitches on the bus
tpm: st33zp24: fix potential buffer overruns caused by bit glitches on the bus
tpm_i2c_infineon: fix potential buffer overruns caused by bit glitches on the bus
tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches on the bus
tpm_tis: fix potential buffer overruns caused by bit glitches on the bus
drivers/char/tpm/st33zp24/st33zp24.c | 4 ++--
drivers/char/tpm/tpm-interface.c | 4 ++++
drivers/char/tpm/tpm2-cmd.c | 4 ++++
drivers/char/tpm/tpm_i2c_infineon.c | 5 +++--
drivers/char/tpm/tpm_i2c_nuvoton.c | 8 ++++++--
drivers/char/tpm/tpm_tis_core.c | 5 +++--
6 files changed, 22 insertions(+), 8 deletions(-)
next reply other threads:[~2018-02-26 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 12:41 Jarkko Sakkinen [this message]
2018-02-26 18:52 ` [GIT PULL] tpmdd fixes for 4.16 James Morris
2018-02-26 19:49 ` James Bottomley
2018-02-26 23:33 ` James Morris
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=20180226124144.GA8675@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.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).