From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Peter.Huewe@infineon.com
Cc: key@linux.vnet.ibm.com, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [PATCH] TPM: Let the tpm char device be openable multiple times
Date: Mon, 15 Oct 2012 10:39:45 -0600 [thread overview]
Message-ID: <20121015163945.GA32563@obsidianresearch.com> (raw)
In-Reply-To: <74A44E99E3274B4CB570415926B37D440ED140@MUCSE501.eu.infineon.com>
On Mon, Oct 15, 2012 at 08:35:09AM +0000, Peter.Huewe@infineon.com wrote:
> > From: Jason Gunthorpe [mailto:jgunthorpe@obsidianresearch.com]
>
> > Using open/close is an interesting idea, but it wouldn't work. open()
> > is coded to return EBUSY if another process has it open, rather than
> > block, and spinning on open would be unacceptable.
>
> Hmm, maybe write a small pass through program which opens /dev/tpm
> once and accepts its data via a socket or pipe?
I believe the kernel should not be enforcing this kind of policy into
userspace. Plus, some of our embedded system are memory constrained
so an unnecessary process is not welcome..
Jason
next prev parent reply other threads:[~2012-10-15 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 23:33 [PATCH] TPM: Let the tpm char device be openable multiple times 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 [this message]
2012-10-15 16:49 ` Alan Cox
2012-10-15 16:56 ` Jason Gunthorpe
2012-10-15 22:02 ` Kent Yoder
-- strict thread matches above, loose matches on Subject: below --
2009-11-03 0:35 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
2009-11-04 9:58 ` Alan Cox
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=20121015163945.GA32563@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=Peter.Huewe@infineon.com \
--cc=key@linux.vnet.ibm.com \
--cc=linux-kernel@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