linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] ima: Use tpm_default_chip() and call TPM functions with a tpm_chip
Date: Tue, 03 Jul 2018 19:32:07 +0300	[thread overview]
Message-ID: <1a5b3d6cddba2d8bc74e5025a628aee7867a8987.camel@linux.intel.com> (raw)
In-Reply-To: <1530550839.3709.46.camel@linux.vnet.ibm.com>

On Mon, 2018-07-02 at 13:00 -0400, Mimi Zohar wrote:
> On Mon, 2018-07-02 at 11:24 -0400, Stefan Berger wrote:
> > Rather than accessing the TPM functions by passing a NULL pointer for
> > the tpm_chip, which causes a lookup for a suitable chip every time, get a
> > hold of a tpm_chip and access the TPM functions using it. Also get rid of
> > the ima_used_chip variable and use the new ima_tpm_chip variable instead
> > for determining whether to call TPM functions.
> > 
> > Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
> > Acked-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> 
> Signed-off-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
> 
> Jarkko, would you mind staging this patch with the rest of the patch
> set?

Yes, sure, I can do that. Any additional tag?

/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-07-03 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 15:24 [PATCH] ima: Use tpm_default_chip() and call TPM functions with a tpm_chip Stefan Berger
2018-07-02 17:00 ` Mimi Zohar
2018-07-03 16:32   ` Jarkko Sakkinen [this message]
2018-07-04 12:10     ` Mimi Zohar
2018-07-05 15:43       ` 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=1a5b3d6cddba2d8bc74e5025a628aee7867a8987.camel@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=linux-security-module@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).