linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: "florian.manoel@siemens.com" <florian.manoel@siemens.com>,
	apronin@chromium.org
Cc: "linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>,
	"Fuchs, Andreas" <andreas.fuchs@sit.fraunhofer.de>,
	"Peter.Huewe@infineon.com" <Peter.Huewe@infineon.com>,
	"joshz@google.com" <joshz@google.com>
Subject: Re: TPM V2: kernel panic on linux reboot
Date: Sat, 13 Feb 2021 01:46:08 +0200	[thread overview]
Message-ID: <YCcTQFkAy+JMp7a5@kernel.org> (raw)
In-Reply-To: <AM0PR10MB254856FDA3E44D4373C17451848B9@AM0PR10MB2548.EURPRD10.PROD.OUTLOOK.COM>

On Fri, Feb 12, 2021 at 07:20:02AM +0000, florian.manoel@siemens.com wrote:
> Hi,
> 
> => Last update and happy end
> 
> To remember what the issue was : kernel panic on reboot on a custom board equipped with CPU NXP LS1043a and TMP V2.0 Infineon slb9670 (spi interface).
> What we did but didn't fix the issue : update our kernel to 5.10.8 => panic still occurs
> What we did and fix the issue => use this patch : https://lkml.org/lkml/2020/7/9/1242

Andrey,

I re-read the thread, and it's been a while and I'm not sure if
I fully get my old review comments.

Your commit message refers to these commits:

A. b4c6230bb0ba spi: Fix controller unregister order
B. f40913d2dca1 spi: pxa2xx: Fix controller unregister order

So I presume that either A or B causes this sequence to trigger:

1. tpm_class_shutdown()
2. tpm_del_char_device()

... and either A or B causes this sequence to trigger:

1. tpm_class_shutdown()
2. tpm_del_char_device()

So:

- Does that fix bundle two separate bug fixes, and if yes, which
  on is associated with which?
- Why do they cause the sequences to trigger, and why these sequences
  did not trigger before?

/Jarkko

      reply	other threads:[~2021-02-12 23:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VI1PR10MB2559EB47FE26FA85EB4B4D4484A70@VI1PR10MB2559.EURPRD10.PROD.OUTLOOK.COM>
2021-01-15  7:17 ` AW: TPM V2: kernel panic on linux reboot florian.manoel
2021-01-17 18:35   ` Jarkko Sakkinen
2021-01-27 14:51     ` AW: " florian.manoel
2021-01-29 23:25       ` Jarkko Sakkinen
2021-02-12  7:20         ` AW: " florian.manoel
2021-02-12 23:46           ` 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=YCcTQFkAy+JMp7a5@kernel.org \
    --to=jarkko@kernel.org \
    --cc=Peter.Huewe@infineon.com \
    --cc=andreas.fuchs@sit.fraunhofer.de \
    --cc=apronin@chromium.org \
    --cc=florian.manoel@siemens.com \
    --cc=joshz@google.com \
    --cc=linux-integrity@vger.kernel.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).