From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
keyrings@vger.kernel.org, James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Andrew Zaborowski <andrew.zaborowski@intel.com>
Subject: [GIT PULL] TPM DEVICE DRIVER updates for v5.17
Date: Wed, 29 Dec 2021 04:33:21 +0200 [thread overview]
Message-ID: <YcvI8Uki51C2aMqe@iki.fi> (raw)
Hi,
Other than bug fixes for TPM, includes a patch for asymmetric keys to allow
to look up and verify with self-signed certificates (keys without so called
Authority Key Identifier (AKID)) using a new "dn:" prefix in the query.
BR,
Jarkko
The following changes since commit e7c124bd04631973a3cc0df19ab881b56d8a2d50:
Merge tag 'selinux-pr-20211228' of git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux (2021-12-28 13:33:06 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git/ tags/tpmdd-next-v5.17
for you to fetch changes up to 035d19ee9b906f8a6937d44cc1dd1bf065be8641:
tpm: fix NPE on probe for missing device (2021-12-29 03:44:50 +0200)
----------------------------------------------------------------
tpmdd updates for Linux v5.17
----------------------------------------------------------------
Andrew Zaborowski (1):
keys: X.509 public key issuer lookup without AKID
AngeloGioacchino Del Regno (1):
tpm: tpm_tis_spi_cr50: Add default RNG quality
Chen Jun (1):
tpm: add request_locality before write TPM_INT_ENABLE
Christophe Jaillet (1):
tpm_tis: Fix an error handling path in 'tpm_tis_core_init()'
Lino Sanfilippo (1):
tpm: fix potential NULL pointer access in tpm_del_char_device
Patrick Williams (1):
tpm: fix NPE on probe for missing device
Rob Barnes (1):
char: tpm: cr50: Set TPM_FIRMWARE_POWER_MANAGED based on device property
Sohaib Mohamed (1):
tpm/st33zp24: drop unneeded over-commenting
axelj (1):
tpm: Add Upgrade/Reduced mode support for TPM2 modules
crypto/asymmetric_keys/asymmetric_type.c | 57 ++++++++++----
crypto/asymmetric_keys/pkcs7_trust.c | 6 +-
crypto/asymmetric_keys/restrict.c | 48 +++++++-----
crypto/asymmetric_keys/x509_cert_parser.c | 10 +++
crypto/asymmetric_keys/x509_public_key.c | 10 +++
drivers/char/tpm/st33zp24/st33zp24.c | 122 +++++-------------------------
drivers/char/tpm/tpm-chip.c | 37 ++++++---
drivers/char/tpm/tpm-sysfs.c | 3 +
drivers/char/tpm/tpm2-cmd.c | 6 ++
drivers/char/tpm/tpm_tis_core.c | 14 +++-
drivers/char/tpm/tpm_tis_i2c_cr50.c | 16 +++-
drivers/char/tpm/tpm_tis_spi_cr50.c | 20 ++++-
include/crypto/public_key.h | 2 +-
include/keys/asymmetric-type.h | 3 +-
include/linux/tpm.h | 10 +++
15 files changed, 205 insertions(+), 159 deletions(-)
next reply other threads:[~2021-12-29 2:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 2:33 Jarkko Sakkinen [this message]
2022-01-06 19:10 ` [GIT PULL] TPM DEVICE DRIVER updates for v5.17 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=YcvI8Uki51C2aMqe@iki.fi \
--to=jarkko@kernel.org \
--cc=andrew.zaborowski@intel.com \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=torvalds@linux-foundation.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