linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nayna <nayna@linux.vnet.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>,
	"Sachin Sant" <sachinp@linux.vnet.ibm.com>
Cc: nayna@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	Mimi Zohar <zohar@linux.ibm.com>,
	gcwilson@linux.ibm.com
Subject: Re: Kernel Bug/oops during boot (PowerVM LPAR w/vTPM)
Date: Wed, 3 Jul 2019 23:36:29 -0400	[thread overview]
Message-ID: <b79528a7-102b-bcd2-43af-27ffa8b1c900@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190703231559.29d54c5c@kitsune.suse.cz>

Hi Sachin and Michal,


On 07/03/2019 05:15 PM, Michal Suchánek wrote:
> On Wed, 3 Jul 2019 13:17:16 +0200
> Michal Suchánek <msuchanek@suse.de> wrote:
>
>> On Wed, 3 Jul 2019 15:54:59 +0530
>> Sachin Sant <sachinp@linux.vnet.ibm.com> wrote:
>>
>>> Booting mainline kernel on PowerVM LPAR with vTPM enabled results
>>> into a kernel crash.
>>>
>>> [    0.365989] BUG: Kernel NULL pointer dereference at 0x00000012
> ...
>>> [    0.366085] NIP [c00000000073dd80] tpm1_pcr_extend+0x130/0x230
>>> [    0.366090] LR [c00000000073dcd0] tpm1_pcr_extend+0x80/0x230
> ...
>> You need to revert (or fix up) commit 0b6cf6b97b7e ("tpm: pass an array
>> of tpm_extend_digest structures to tpm_pcr_extend()". At least
>> reverting it fixes the issue for me.
> FTR this is the revert on lkml https://lkml.org/lkml/2019/7/1/423
>
>


I have just now posted the fix for this to the mailing list and copied 
both of you. I would appreciate your testing and confirming that the 
patch "tpm: fixes uninitialized allocated banks for IBM vtpm driver" 
addresses this bug.

Thanks & Regards,
       - Nayna



      reply	other threads:[~2019-07-04  3:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 10:24 Kernel Bug/oops during boot (PowerVM LPAR w/vTPM) Sachin Sant
2019-07-03 11:17 ` Michal Suchánek
2019-07-03 21:15   ` Michal Suchánek
2019-07-04  3:36     ` Nayna [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=b79528a7-102b-bcd2-43af-27ffa8b1c900@linux.vnet.ibm.com \
    --to=nayna@linux.vnet.ibm.com \
    --cc=gcwilson@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    --cc=nayna@linux.ibm.com \
    --cc=sachinp@linux.vnet.ibm.com \
    --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 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).