From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Valdis.Kletnieks@vt.edu
Cc: Hal Finney <hal.finney@gmail.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
srajiv@linux.vnet.ibm.com
Subject: Re: [tpmdd-devel] [PATCH] TPM: Let the tpm char device be openable multiple times
Date: Tue, 3 Nov 2009 21:27:17 -0700 [thread overview]
Message-ID: <20091104042717.GS1966@obsidianresearch.com> (raw)
In-Reply-To: <13189.1257305069@turing-police.cc.vt.edu>
On Tue, Nov 03, 2009 at 10:24:29PM -0500, Valdis.Kletnieks@vt.edu wrote:
> A number of other things under drivers/ implement "only one open" semantics,
> but those are hard-coded into the driver. But for the TPM, it's unclear if
> exclusive or non-exclusive is the right model.
The underlying hardware already supports multiplexing multiple clients
in the same command stream - I'm not sure why this shouldn't be
exported to user space as-is. The kernel already accesses the TPM
without going through the middleware for in kernel features..
> Maybe the right answer is to default to multiple opens, but have an
> ioctl() that turns on exclusive mode. If you have a 'tcsd' daemon,
> it will need to get launched early enough to do the open/ioctl
Why is this an issue? /dev/tpm is root only accessible. There are a lot
of things that can go horribly wrong if root does improper things, and
you can create quite reasonable multi-process tpm using applications
without the middleware.
Even if another root process does open /dev/tpm - what is the worst it
can do?
Jason
next prev parent reply other threads:[~2009-11-04 4:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 0:35 [PATCH] TPM: Let the tpm char device be openable multiple times Jason Gunthorpe
2009-11-03 10:43 ` Alan Cox
2009-11-03 17:15 ` Jason Gunthorpe
2009-11-03 17:31 ` [tpmdd-devel] " Hal Finney
2009-11-03 17:46 ` Jason Gunthorpe
2009-11-03 18:14 ` Valdis.Kletnieks
2009-11-03 22:41 ` Jason Gunthorpe
2009-11-04 3:24 ` Valdis.Kletnieks
2009-11-04 4:27 ` Jason Gunthorpe [this message]
2009-11-04 9:58 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2012-09-30 23:33 Jason Gunthorpe
2012-10-01 9:07 ` [tpmdd-devel] " Peter.Huewe
2012-10-01 16:09 ` Jason Gunthorpe
2012-10-10 16:33 ` Kent Yoder
2012-10-12 20:56 ` Jason Gunthorpe
2012-10-15 8:35 ` [tpmdd-devel] " Peter.Huewe
2012-10-15 16:39 ` Jason Gunthorpe
2012-10-15 16:49 ` Alan Cox
2012-10-15 16:56 ` Jason Gunthorpe
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=20091104042717.GS1966@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=hal.finney@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srajiv@linux.vnet.ibm.com \
--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.