All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: tpmdd-devel@lists.sourceforge.net,
	linux-security-module@vger.kernel.org,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [tpmdd-devel] [PATCH 2/2] tpm2: context save and restore space managed sessions
Date: Thu, 19 Jan 2017 07:13:12 -0500	[thread overview]
Message-ID: <1484827992.3140.9.camel@HansenPartnership.com> (raw)
In-Reply-To: <20170119120400.ntvkkukm6oektvnj@intel.com>

On Thu, 2017-01-19 at 14:04 +0200, Jarkko Sakkinen wrote:
> On Wed, Jan 18, 2017 at 10:10:42AM -0500, James Bottomley wrote:
> > Now that sessions are isolated, we can introduce a session_buf in 
> > the tpm2 space to save and restore them.  This allows us to have 
> > many more sessions active simultaneously (up to 
> > TPM_PT_MAX_SESSIONS).  As part of this, we must intercept and 
> > manually remove contexts for flushed sessions.
> 
> Again I don't understand the interception part. Like with transient
> objects I just catch TPM_RC_HANDLE error and forget them in the save
> part.

it's for the global session tracking patch (see other email for
details)

> PS. Do you mind if I take part of the patch that encapsulates a
> single context save as of my patch that implements transient object
> swapping? It merely moves the code in there to a different location.
> Would just make the patch set cleaner. I would do this for v4 of the
> patch set.

Sure.  Rebase should be able to do this easily for me.

James

      reply	other threads:[~2017-01-19 12:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 15:08 [PATCH 0/2] Add session isolation and context saving to the space manager James Bottomley
2017-01-18 15:08 ` James Bottomley
     [not found] ` <1484752097.2717.14.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-18 15:09   ` [PATCH 1/2] tpm2: add session handle isolation to tpm spaces James Bottomley
2017-01-18 15:09     ` James Bottomley
2017-01-19 11:58     ` [tpmdd-devel] " Jarkko Sakkinen
     [not found]       ` <20170119115812.vqaoxv77mgnuq43h-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-19 12:11         ` James Bottomley
2017-01-19 12:11           ` [tpmdd-devel] " James Bottomley
     [not found]           ` <1484827883.3140.7.camel-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
2017-01-20 13:23             ` Jarkko Sakkinen
2017-01-20 13:23               ` [tpmdd-devel] " Jarkko Sakkinen
     [not found]               ` <20170120132331.74dixmuj6htzgr4z-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-20 14:27                 ` Ken Goldman
2017-01-20 20:51                   ` Jarkko Sakkinen
2017-01-20 20:51                     ` [tpmdd-devel] " Jarkko Sakkinen
2017-01-20 14:39                 ` James Bottomley
2017-01-20 14:39                   ` [tpmdd-devel] " James Bottomley
2017-01-20 17:57                   ` Jarkko Sakkinen
2017-01-18 15:10   ` [PATCH 2/2] tpm2: context save and restore space managed sessions James Bottomley
2017-01-18 15:10     ` James Bottomley
2017-01-19 12:04     ` [tpmdd-devel] " Jarkko Sakkinen
2017-01-19 12:13       ` James Bottomley [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=1484827992.3140.9.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.