From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org
Cc: David Howells <dhowells@redhat.com>,
Mimi Zohar <zohar@linux.ibm.com>,
James Bottomley <jejb@linux.ibm.com>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Subject: [PATCH v4 0/3,RESEND] KEYS, trusted: a bunch of bug fixes
Date: Fri, 30 Oct 2020 12:17:34 +0200 [thread overview]
Message-ID: <20201030101734.GA59390@kernel.org> (raw)
This patch set contains a bunch of disjoint bug fixes.
v4:
* Do not create stubs for tpm_transmit_cmd(), tpm_try_get_ops() and
tpm_put_ops().
https://lore.kernel.org/linux-integrity/20201013023927.GA71954@linux.intel.com/
v3:
* Reordered patches a bit, i.e. trivial fixes in the head and the least
trivial in the tail.
<no xref>
* Added the missing "return -ENODEV;" to tpm_transmit_cmd(), when the
kernel is compiled without TPM support.
https://lore.kernel.org/linux-integrity/202010110927.zsxMpek2-lkp@intel.com/
v2:
* Fix a kernel test bot warning.
https://lore.kernel.org/linux-integrity/202010051152.9kxy43LO-lkp@intel.com/
Jarkko Sakkinen (3):
KEYS: trusted: Fix incorrect handling of tpm_get_random()
KEYS: trusted: Fix migratable=1 failing
KEYS: trusted: Reserve TPM for seal and unseal operations
drivers/char/tpm/tpm.h | 4 -
include/linux/tpm.h | 5 +-
security/keys/trusted-keys/trusted_tpm1.c | 94 ++++++++++++++++-------
security/keys/trusted-keys/trusted_tpm2.c | 6 +-
4 files changed, 75 insertions(+), 34 deletions(-)
--
2.25.1
next reply other threads:[~2020-10-30 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 10:17 Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-30 8:51 [PATCH v4 0/3,RESEND] KEYS, trusted: a bunch of bug fixes 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=20201030101734.GA59390@kernel.org \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=jejb@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.