From: Jarkko Sakkinen <jarkko@kernel.org>
To: Lino Sanfilippo <LinoSanfilippo@gmx.de>
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, stefanb@linux.vnet.ibm.com,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
p.rosenberger@kunbus.com,
Lino Sanfilippo <l.sanfilippo@kunbus.com>
Subject: Re: [PATCH 3/4] tpm: in tpm2_del_space check if ops pointer is still valid
Date: Tue, 26 Jan 2021 17:29:23 +0200 [thread overview]
Message-ID: <a4ecfaf99f322c752d6422056d4ea94f9b3d962b.camel@kernel.org> (raw)
In-Reply-To: <9bb612ef-75be-f8d4-10a6-7ab5869da18f@gmx.de>
On Sun, 2021-01-24 at 17:47 +0100, Lino Sanfilippo wrote:
>
> Hi Jarkko,
>
> On 17.01.21 at 19:13, Jarkko Sakkinen wrote:
> >
> > I have hard time to believe that any of these patches are based on
> > actual regressions.
> >
> > /Jarko
> >
>
> patch 1 is indeed wrong (I oversaw the action call in case of error),
> so please ignore it.
>
> However patches 2 and 3 are based on bugs I encountered while working with
> TPM. I am sorry if I did not make the issues clear enough in the patches
> commit messages. Let me try to explain it in more detail:
>
> The bugs showed up after unloading the TPM chip driver module while one
> process still had the /dev/tpmrm device open.
Please refine the patch set, and we will look into that then.
Put fixes tags and logs where appropriate. Thanks.
/Jarkko
next prev parent reply other threads:[~2021-01-26 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 1:22 [PATCH 0/4] TPM fixes Lino Sanfilippo
2021-01-16 1:22 ` [PATCH 1/4] tpm: in case of error properly cleanup in tpmm_chip_alloc Lino Sanfilippo
2021-01-17 18:08 ` Jarkko Sakkinen
2021-01-16 1:22 ` [PATCH 2/4] tpm: fix reference counting for struct tpm_chip Lino Sanfilippo
2021-01-17 18:11 ` Jarkko Sakkinen
2021-01-16 1:22 ` [PATCH 3/4] tpm: in tpm2_del_space check if ops pointer is still valid Lino Sanfilippo
2021-01-17 18:13 ` Jarkko Sakkinen
2021-01-24 16:47 ` Lino Sanfilippo
2021-01-26 15:29 ` Jarkko Sakkinen [this message]
2021-01-27 15:14 ` Lino Sanfilippo
2021-01-16 1:22 ` [PATCH 4/4] tpm: Provide a function tpm_chip_free() to free tpm chips Lino Sanfilippo
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=a4ecfaf99f322c752d6422056d4ea94f9b3d962b.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=LinoSanfilippo@gmx.de \
--cc=jgg@ziepe.ca \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.rosenberger@kunbus.com \
--cc=peterhuewe@gmx.de \
--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).