From: Jarkko Sakkinen <jarkko@kernel.org>
To: Lukasz Majczak <lma@semihalf.com>
Cc: Dirk Gouders <dirk@gouders.net>,
Guenter Roeck <linux@roeck-us.net>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Tj <ml.linux@elloe.vision>, Peter Huewe <peterhuewe@gmx.de>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Radoslaw Biernacki <rad@semihalf.com>,
Marcin Wojtas <mw@semihalf.com>, Alex Levin <levinale@google.com>
Subject: Re: [PATCH v3] tpm_tis: Add missing tpm_request/relinquish_locality calls
Date: Thu, 4 Feb 2021 01:24:04 +0200 [thread overview]
Message-ID: <YBswlPuVINENIoUC@kernel.org> (raw)
In-Reply-To: <CAFJ_xbpv3O5f4MPUhZExA3g-4NjPN_vvv7q6Srh1ddqCH4ie9w@mail.gmail.com>
On Wed, Feb 03, 2021 at 02:43:44PM +0100, Lukasz Majczak wrote:
> Hi Jarkko, Dirk,
>
> Jarkko,
> Thank you for your points - I will try to fix all you have mentioned.
> I think it would be good to clarify a few things, before going with
> the next version. Regarding use tpm_chip_start/stop() around
> tpm2_probe() call - I have followed the similar way it is done in the
> probe_itpm() function, where is also a call to tpm_tis_send_data()
> guarded by request/release_locality(). I have tested it on the Samsung
> Chromebook Pro (which reports TPM 1.2 / Cr50) and it was sufficient
> (e.g. I didn't have to enable the clock) to get rid of a trace
> mentioned in the commit message....but now writing these words I'm
> starting to think that using tpm_chip_start/stop() could be safer from
> a point of view of other TPMs... so if you suggest using
> tpm_chip_start/stop() shall I also add it to the probe_itpm() (instead
> of request/release_locality()) ?
>
> Dirk,
> Thanks for the clarification. Regarding the issue you observe - I
> wanted to address at first the one that is generating the trace
> (please check the commit message) because it was leading to returning
> an error in the tpm_tis_status() function causing TPM module not
> initialized at all in the end - requesting locality before the call to
> the tpm_tis_send_data() has helped in my case (my test environment). I
> am aware of the second issue - "TPM interrupt not working, polling
> instead", but as it is not as critical as the first one, I decided to
> work on it later.
>
> Thank you once again for all your input and sorry for a confusion with
> sending patches.
NP, thanks for doing this. Just take your time and polish the cosmetic
things. Especially for bug fixes a clean changelog is essential.
> Best regards,
> Lukasz
/Jarkko
next prev parent reply other threads:[~2021-02-03 23:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 1:42 [PATCH] tpm_tis: Add missing start/stop_tpm_chip calls Lukasz Majczak
2021-01-25 17:12 ` Jarkko Sakkinen
2021-01-25 17:18 ` Guenter Roeck
2021-01-26 15:46 ` Łukasz Majczak
2021-01-26 16:46 ` James Bottomley
2021-01-26 18:55 ` Tj (Elloe Linux)
2021-01-28 5:58 ` Jarkko Sakkinen
2021-01-29 22:59 ` Jarkko Sakkinen
2021-01-29 23:00 ` Jarkko Sakkinen
2021-01-30 23:49 ` Guenter Roeck
2021-01-31 0:41 ` James Bottomley
2021-01-31 3:36 ` Guenter Roeck
2021-01-31 4:18 ` James Bottomley
2021-02-02 16:17 ` Jarkko Sakkinen
2021-02-02 15:33 ` Jarkko Sakkinen
2021-01-29 22:49 ` Jarkko Sakkinen
2021-01-29 23:32 ` Guenter Roeck
2021-01-28 13:07 ` [PATCH v2] tpm_tis: Add missing tpm_request/relinquish_locality calls Lukasz Majczak
2021-01-28 17:37 ` Guenter Roeck
2021-01-30 20:40 ` Jarkko Sakkinen
2021-01-30 20:47 ` Jarkko Sakkinen
[not found] ` <ghwnvtwifq.fsf@gouders.net>
2021-02-02 16:29 ` Jarkko Sakkinen
2021-02-02 15:51 ` [PATCH v3] " Lukasz Majczak
2021-02-02 16:29 ` Guenter Roeck
2021-02-02 22:35 ` Jarkko Sakkinen
2021-02-02 18:47 ` Dirk Gouders
2021-02-03 11:46 ` Dirk Gouders
2021-02-03 13:43 ` Lukasz Majczak
2021-02-03 23:24 ` Jarkko Sakkinen [this message]
2021-02-02 19:57 ` [PATCH v4] " Lukasz Majczak
2021-02-02 21:49 ` Jarkko Sakkinen
2021-02-02 21:49 ` [PATCH v3] " Jarkko Sakkinen
2021-02-03 0:05 ` Jarkko Sakkinen
2021-02-03 0:07 ` Jarkko Sakkinen
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=YBswlPuVINENIoUC@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dirk@gouders.net \
--cc=jgg@ziepe.ca \
--cc=levinale@google.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lma@semihalf.com \
--cc=ml.linux@elloe.vision \
--cc=mw@semihalf.com \
--cc=peterhuewe@gmx.de \
--cc=rad@semihalf.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).