From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Ken Goldman <kgoldman@us.ibm.com>
Cc: tpmdd-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [PATCH 1/2] tpm2: add session handle isolation to tpm spaces
Date: Fri, 20 Jan 2017 22:51:00 +0200 [thread overview]
Message-ID: <20170120205100.h36r2qr6vrxj3zim@intel.com> (raw)
In-Reply-To: <o5t6ns$k6e$1@blaine.gmane.org>
On Fri, Jan 20, 2017 at 09:27:25AM -0500, Ken Goldman wrote:
> On 1/20/2017 8:23 AM, Jarkko Sakkinen wrote:
> >
> > I'm talking about not trying to detect if something gets deleted. When
> > something gets created you would go through the global list of sessions
> > and check if it is used. If so, it must be that the session was deleted
> > at some point.
>
> Are you saying that, when a process flushes (or continue = false) a
> session, this code won't actually flush the context? You'll wait until
> another startauthsession creates a handle, and then delete other
> occurrences of it?
I just wouldn't get care if a session gets deleted. You can detect it
postmortem when something gets created with the same handle.
/Jarkko
next prev parent reply other threads:[~2017-01-20 20:51 UTC|newest]
Thread overview: 11+ 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:09 ` [PATCH 1/2] tpm2: add session handle isolation to tpm spaces James Bottomley
2017-01-19 11:58 ` [tpmdd-devel] " Jarkko Sakkinen
2017-01-19 12:11 ` James Bottomley
2017-01-20 13:23 ` Jarkko Sakkinen
2017-01-20 14:39 ` James Bottomley
2017-01-20 17:57 ` Jarkko Sakkinen
[not found] ` <o5t6ns$k6e$1@blaine.gmane.org>
2017-01-20 20:51 ` Jarkko Sakkinen [this message]
2017-01-18 15:10 ` [PATCH 2/2] tpm2: context save and restore space managed sessions James Bottomley
2017-01-19 12:04 ` [tpmdd-devel] " Jarkko Sakkinen
2017-01-19 12:13 ` James Bottomley
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=20170120205100.h36r2qr6vrxj3zim@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=kgoldman@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®