linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Stefan Berger <stefanb@linux.ibm.com>,
	peterhuewe@gmx.de, jarkko@kernel.org, jgg@ziepe.ca
Cc: stefanb@linux.vnet.ibm.com,
	James.Bottomley@hansenpartnership.com, David.Laight@ACULAB.COM,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	p.rosenberger@kunbus.com
Subject: Re: [PATCH v8 0/1] tpm: fix reference counting for struct tpm_chip
Date: Tue, 1 Mar 2022 16:45:59 +0100	[thread overview]
Message-ID: <fbb0a768-dbef-bb6e-f77b-f40a4da7f8bb@gmx.de> (raw)
In-Reply-To: <a7a2c56c-a82b-40a9-68e5-7e6d92427c70@linux.ibm.com>

On 01.03.22 at 14:56, Stefan Berger wrote:

>
> We also need to apply this patch here to fix another crash:
>
> https://lore.kernel.org/all/20210615091410.17007-2-vincent.whitchurch@axis.com/
>

Right, this is another issue that should be fixed. The bugfix you mention is essentially the same
as James proposed over two years ago:

https://lore.kernel.org/linux-integrity/e7566e1e48f5be9dca034b4bfb67683b5d3cb88f.camel@HansenPartnership.com/

Regards,
Lino






      reply	other threads:[~2022-03-01 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  2:21 [PATCH v8 0/1] tpm: fix reference counting for struct tpm_chip Lino Sanfilippo
2022-03-01  2:21 ` [PATCH v8 1/1] " Lino Sanfilippo
2022-03-01 12:36   ` Stefan Berger
2022-03-01 15:39     ` Lino Sanfilippo
2022-03-03 22:41     ` Jarkko Sakkinen
2022-03-01 14:05   ` Jason Gunthorpe
2022-03-01 16:18     ` Lino Sanfilippo
2022-03-01 13:56 ` [PATCH v8 0/1] " Stefan Berger
2022-03-01 15:45   ` Lino Sanfilippo [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=fbb0a768-dbef-bb6e-f77b-f40a4da7f8bb@gmx.de \
    --to=linosanfilippo@gmx.de \
    --cc=David.Laight@ACULAB.COM \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.rosenberger@kunbus.com \
    --cc=peterhuewe@gmx.de \
    --cc=stefanb@linux.ibm.com \
    --cc=stefanb@linux.vnet.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).