From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
tomas.winkler@intel.com, Jason Gunthorpe <jgg@ziepe.ca>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: Getting weird TPM error after rebasing my tree to security/next-general
Date: Fri, 1 Feb 2019 13:40:41 +0200 [thread overview]
Message-ID: <20190201114041.GA15858@linux.intel.com> (raw)
In-Reply-To: <20190131233136.3dhadb7a46lp2nu6@cantor>
On Thu, Jan 31, 2019 at 04:31:36PM -0700, Jerry Snitselaar wrote:
> On Thu Jan 31 19, Linus Torvalds wrote:
> > On Thu, Jan 31, 2019 at 12:47 PM Jarkko Sakkinen
> > <jarkko.sakkinen@linux.intel.com> wrote:
> > >
> > > I'll try it first thing when I wake up tomorrow (11PM in Finland ATM).
> >
> > Thanks.
> >
> > > Appreciate for taking time on this.
> >
> > Hey, it was my commit that broke it for you. Even if it happened to
> > work before, and only did so by pure luck, it was a functional
> > regression.
> >
> > I get very upset when other developers don't step up when *their*
> > changes break something, and I don't consider "it shouldn't have
> > worked in the first place" to be a valid excuse. You broke it, you'd
> > better fix it.
> >
> > So I had better fix my own mess too, in order to not look too hypocritical.
> >
> > And I was very aware that hardcoding the memcpy_*io() access patterns
> > might break something. I just _hoped_ it wouldn't, because we actually
> > ended up going back to the very original access patterns (but it was
> > from a long long time ago).
> >
> > In fact, while it's slightly annoying, in many ways it's actually good
> > that we found breakage, and could pinpoint exactly *why* it broke.
> > That does validate the whole "we shouldn't just depend on the random
> > implementation detail of 'memcpy()'" argument.
> >
> > So I'll wait to hear back whether that patch fixes things for you, but
> > I _think_ it will, and we'll be better off in the long range with this
> > whole thing.
> >
> > Linus
>
> I just did a quick test here of booting and running a couple commands
> (tpm2_getcap, tpm2_pcrlist), and the patch seems to work for me. I was
> seeing the error during tpm_crb initialization without the patch.
Works for me too. Just submitted tpm_crb level fix too for the reasons
explained in accompanied commit message.
Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
/Jarkko
next prev parent reply other threads:[~2019-02-01 11:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 14:25 Getting weird TPM error after rebasing my tree to security/next-general Jarkko Sakkinen
2019-01-18 22:09 ` James Bottomley
2019-01-20 16:04 ` Jarkko Sakkinen
2019-01-22 1:02 ` Jarkko Sakkinen
2019-01-22 2:58 ` Jason Gunthorpe
2019-01-22 13:29 ` Jarkko Sakkinen
2019-01-22 18:26 ` Linus Torvalds
2019-01-23 15:36 ` Jarkko Sakkinen
2019-01-23 18:43 ` Linus Torvalds
2019-01-29 13:20 ` Jarkko Sakkinen
2019-01-31 12:26 ` Jarkko Sakkinen
2019-01-31 16:04 ` Jarkko Sakkinen
2019-01-31 17:06 ` Jarkko Sakkinen
2019-01-31 17:43 ` Linus Torvalds
2019-01-31 18:47 ` Jarkko Sakkinen
2019-01-31 18:35 ` Jarkko Sakkinen
2019-01-31 18:51 ` Linus Torvalds
2019-01-31 18:52 ` Linus Torvalds
2019-01-31 19:10 ` Linus Torvalds
2019-01-31 19:47 ` Winkler, Tomas
2019-02-01 8:12 ` Jarkko Sakkinen
2019-01-31 20:07 ` Winkler, Tomas
2019-01-31 20:47 ` Jarkko Sakkinen
2019-01-31 21:58 ` Linus Torvalds
2019-01-31 23:31 ` Jerry Snitselaar
2019-02-01 11:40 ` Jarkko Sakkinen [this message]
2019-01-31 20:45 ` Jarkko Sakkinen
2019-02-01 18:04 ` Linus Torvalds
2019-02-04 11:58 ` Jarkko Sakkinen
2019-01-23 20:11 ` 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=20190201114041.GA15858@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).