tpmdd-devel Archive mirror
 help / color / mirror / Atom feed
From: Ken Goldman <kgold-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: TPM resource manager - persistent objects should be global
Date: Tue, 28 Mar 2017 17:39:52 -0400	[thread overview]
Message-ID: <e89db1e1-7996-3106-c034-e6d4c2c5f887@linux.vnet.ibm.com> (raw)

I have a persistent object at 81000001.

getcapability through /dev/tpm0 shows it.  The same command through 
/dev/tpmrm0 does not.  This causes further problems in the application.

While transient objects are per connection, IMHO persistent objects 
should be global.

~~

Warning:  I think I'm using the latest TPM device driver from

git://git.infradead.org/users/jjs/linux-tpmdd.git

but I'm new to both git and kernel building, so I could be wrong.  If 
you think the above should work, it could be my error.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

             reply	other threads:[~2017-03-28 21:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 21:39 Ken Goldman [this message]
     [not found] ` <e89db1e1-7996-3106-c034-e6d4c2c5f887-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-03-29 18:40   ` TPM resource manager - persistent objects should be global James Bottomley
     [not found]     ` <1490812802.5647.4.camel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-03-31  8:14       ` Jarkko Sakkinen
2017-03-31 14:57       ` Ken Goldman
     [not found]         ` <0a9a4380-e7cc-8927-e594-bbf5d9fa60c8-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-03-31 18:28           ` 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=e89db1e1-7996-3106-c034-e6d4c2c5f887@linux.vnet.ibm.com \
    --to=kgold-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).