From: Matthew Garrett <mjg59@srcf.ucam.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de,
jarkko@kernel.org, jgg@ziepe.ca
Subject: Re: Avoiding EBUSY on TPM writes
Date: Fri, 16 Jun 2023 00:54:22 +0100 [thread overview]
Message-ID: <20230615235422.GA15637@srcf.ucam.org> (raw)
In-Reply-To: <d157ccc308103b8bf158c903dfa53ee723db58fb.camel@HansenPartnership.com>
On Thu, Jun 15, 2023 at 07:38:57PM -0400, James Bottomley wrote:
> However, this behaviour is per-fd, why can't you just open multiple
> fd's for your multiple accesses? /dev/tpmrm0 will assure that they
> don't see each other and that the commands are properly sequenced
> without giving you an EBUSY. And bonus you don't have to keep global
> track of how many transient resources you've used.
Argh! Sorry, I'd missed that this was per-fd - that makes complete
sense. Let me figure out why we're re-using the same fd for multiple
requests.
prev parent reply other threads:[~2023-06-15 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 21:09 Avoiding EBUSY on TPM writes Matthew Garrett
2023-06-15 23:38 ` James Bottomley
2023-06-15 23:54 ` Matthew Garrett [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=20230615235422.GA15637@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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 NNTP newsgroup(s).