public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@intel.com>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: jarkko.sakkinen@linux.intel.com,
	jason.gunthorpe@obsidianresearch.com, stefanb@linux.vnet.ibm.com,
	Scot Doyle <lkml14@scotdoyle.com>,
	peterhuewe@gmx.de, tpmdd@selhorst.net,
	tpmdd-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v4.0][v4.1][v4.2][Regression] tpm: fix raciness of PPI interface lookup
Date: Tue, 15 Sep 2015 13:53:32 +0300	[thread overview]
Message-ID: <20150915105332.GA18109@intel.com> (raw)
In-Reply-To: <55F73DC7.4070007@canonical.com>

Hi

Sorry for the late reply. Looking into this now and sending feedback
later today.

/Jarkko

On Mon, Sep 14, 2015 at 05:36:07PM -0400, Joseph Salisbury wrote:
> Hi Jarkko,
> 
> A kernel bug report was opened against Ubuntu [0] and in bugzilla[1].  A
> kernel bisect was performed, and it identified the following commit as
> the first bad commit:
> 
> commit 0dc553652102c55a43eb1ab52e2049e478469f53
> Author: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> Date:   Fri Dec 12 11:46:35 2014 -0800
> 
>     tpm: fix raciness of PPI interface lookup
> 
> 
> The regression was introduced as of v4.0-rc1.
> 
> I was hoping to get your feedback, since you are the patch author.  Do
> you think gathering any additional data will help diagnose this issue,
> or would it be best to submit a revert request?  An issue with the
> revert request is that it would also require reverting several other
> commits that came after this commit or a backport of the revert.
>     
> 
> Thanks,
>     
> Joe
> 
> [0] http://pad.lv/1491467
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=53071
> 

      parent reply	other threads:[~2015-09-15 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 21:36 [v4.0][v4.1][v4.2][Regression] tpm: fix raciness of PPI interface lookup Joseph Salisbury
2015-09-14 22:26 ` Jason Gunthorpe
2015-09-15 10:53 ` Jarkko Sakkinen [this message]

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=20150915105332.GA18109@intel.com \
    --to=jarkko.sakkinen@intel.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jason.gunthorpe@obsidianresearch.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml14@scotdoyle.com \
    --cc=peterhuewe@gmx.de \
    --cc=stefanb@linux.vnet.ibm.com \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=tpmdd@selhorst.net \
    /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