[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190131183530.GA27112@linux.intel.com>
Date: Thu, 31 Jan 2019 20:35:31 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
tomas.winkler@...el.com
Cc: Jason Gunthorpe <jgg@...pe.ca>,
James Bottomley <James.Bottomley@...senpartnership.com>,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: Getting weird TPM error after rebasing my tree to
security/next-general
On Thu, Jan 31, 2019 at 07:06:03PM +0200, Jarkko Sakkinen wrote:
> Found something that *does* fix the issue. If I replace memcpy_*io()
> calls with regular memcpy(), the driver works and all my tests pass.
OK, so the length of the response is not trashed, but only the error
code. The attached patch fully fixes the issue.
Here's the header again:
struct tpm_output_header {
__be16 tag;
__be32 length;
__be32 return_code;
} __packed;
The first to fields *are* read correctly and the last field get 1's
(thus TPM error -1).
With the attached the patch things work properly, but still
unsatisfactory fix (return to old behavior because it seems to
work).
/Jarkko
View attachment "0001-tpm-tpm_crb-Revert-to-memcpy-for-copying-tail-of-the.patch" of type "text/x-diff" (903 bytes)
Powered by blists - more mailing lists