From: Jason Gunthorpe <jgg@ziepe.ca>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: linux-integrity@vger.kernel.org, jarkko.sakkinen@linux.intel.com,
zohar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] tpm: Implement tpm_chip_find() for other subsystems to find a TPM chip
Date: Fri, 22 Jun 2018 15:13:46 -0600 [thread overview]
Message-ID: <20180622211346.GF19151@ziepe.ca> (raw)
In-Reply-To: <6f4d9302-8399-e73a-f8d0-d493658c1980@linux.vnet.ibm.com>
On Fri, Jun 22, 2018 at 04:45:47PM -0400, Stefan Berger wrote:
> On 06/22/2018 04:43 PM, Jason Gunthorpe wrote:
> >On Fri, Jun 22, 2018 at 12:46:11PM -0400, Stefan Berger wrote:
> >>Implement tpm_chip_find() for other subsystems to find a TPM chip and
> >>get a reference to that chip.
> >>
> >>Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> >> drivers/char/tpm/tpm-chip.c | 27 +++++++++++++++++++++++++++
> >> include/linux/tpm.h | 5 +++++
> >> 2 files changed, 32 insertions(+)
> >>
> >>diff --git a/drivers/char/tpm/tpm-chip.c b/drivers/char/tpm/tpm-chip.c
> >>index 4e83695af068..2520555b1e17 100644
> >>+++ b/drivers/char/tpm/tpm-chip.c
> >>@@ -81,6 +81,33 @@ void tpm_put_ops(struct tpm_chip *chip)
> >> EXPORT_SYMBOL_GPL(tpm_put_ops);
> >> /**
> >>+ * tpm_chip_find() - find a TPM chip and get a reference to it
> >>+ */
> >>+struct tpm_chip *tpm_chip_find(void)
> >I feel like this should be called 'tpm_default_chip()'
> >
> >>+{
> >>+ struct tpm_chip *chip, *res = NULL;
> >>+ int chip_num = 0;
> >>+ int chip_prev;
> >>+
> >>+ mutex_lock(&idr_lock);
> >>+
> >>+ do {
> >>+ chip_prev = chip_num;
> >>+ chip = idr_get_next(&dev_nums_idr, &chip_num);
> >>+ if (chip) {
> >>+ get_device(&chip->dev);
> >>+ res = chip;
> >>+ break;
> >>+ }
> >>+ } while (chip_prev != chip_num);
> >>+
> >>+ mutex_unlock(&idr_lock);
> >And what was tpm_chip_find_get should just call this function..
> And then after that each time tpm_get_ops() ?
It is best to keep the tpm_chip_find_get/tpm_put_ops for internal use
as it also manages the kref lifetime of chip in a subtle way, it
relies on the ops lock not the kref to keep the memory valid when it
has a NULL parameter..
Something like this:
struct tpm_chip *tpm_find_get_ops(struct tpm_chip *chip)
{
int rc;
if (chip) {
if (!tpm_try_get_ops(chip))
return NULL;
return chip;
}
chip = tpm_default_chip();
rc = tpm_try_get_ops(chip));
put_device(&chip->dev);
if (rc)
return NULL;
return chip;
}
Jason
next prev parent reply other threads:[~2018-06-22 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 16:46 [PATCH v3 0/4] Have IMA find and use a tpm_chip until system shutdown Stefan Berger
2018-06-22 16:46 ` [PATCH v3 1/4] tpm: rename tpm_chip_find_get() to tpm_get_ops() Stefan Berger
2018-06-22 20:42 ` Jason Gunthorpe
2018-06-22 16:46 ` [PATCH v3 2/4] tpm: Implement tpm_chip_find() for other subsystems to find a TPM chip Stefan Berger
2018-06-22 20:43 ` Jason Gunthorpe
2018-06-22 20:45 ` Stefan Berger
2018-06-22 21:13 ` Jason Gunthorpe [this message]
2018-06-22 16:46 ` [PATCH v3 3/4] ima: Use tpm_chip_find() and call TPM functions with a tpm_chip Stefan Berger
2018-06-22 16:46 ` [PATCH v3 4/4] ima: Get rid of ima_used_chip and use ima_tpm_chip != NULL instead Stefan Berger
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=20180622211346.GF19151@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=zohar@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