From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH v9 2/2] tpm: Add support for event log pointer found in TPM2 ACPI table
Date: Tue, 14 Jul 2020 08:09:03 -0400 [thread overview]
Message-ID: <69907c30-62c2-b4bd-e84f-11612bba9c95@linux.ibm.com> (raw)
In-Reply-To: <20200714112030.GA1448526@linux.intel.com>
On 7/14/20 7:20 AM, Jarkko Sakkinen wrote:
> On Wed, Jul 08, 2020 at 10:17:17AM -0400, Stefan Berger wrote:
>>> ❯ swtpm-mvo.swtpm socket --tpmstate dir=/tmp/mytpm1 \
>>> --ctrl type=unixio,path=/tmp/mytpm1/swtpm-sock \
>>> --log level=20
>>> swtpm: Could not open UnixIO socket: No such file or directory
>>
>> Did you create the directory '/tmp/mytpm1' ?
> Yes. It's the socket file that it is complain because it does
> not exist beforehand.
The socket file is created by the swtpm program.
>
> /Jarkko
next prev parent reply other threads:[~2020-07-14 12:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 18:19 [PATCH v9 0/2] tpm2: Make TPM2 logs accessible for non-UEFI firmware Stefan Berger
2020-07-06 18:19 ` [PATCH v9 1/2] acpi: Extend TPM2 ACPI table with missing log fields Stefan Berger
2020-07-06 22:02 ` Jerry Snitselaar
2020-07-06 18:19 ` [PATCH v9 2/2] tpm: Add support for event log pointer found in TPM2 ACPI table Stefan Berger
2020-07-06 22:04 ` Jerry Snitselaar
2020-07-06 23:09 ` Jarkko Sakkinen
2020-07-06 23:12 ` Jarkko Sakkinen
2020-07-06 23:55 ` Stefan Berger
2020-07-07 2:24 ` Jarkko Sakkinen
2020-07-07 3:08 ` Stefan Berger
2020-07-07 4:03 ` Jarkko Sakkinen
2020-07-07 4:09 ` Stefan Berger
2020-07-08 14:07 ` Jarkko Sakkinen
2020-07-08 14:17 ` Stefan Berger
2020-07-14 11:20 ` Jarkko Sakkinen
2020-07-14 12:09 ` Stefan Berger [this message]
2020-07-16 17:26 ` Jarkko Sakkinen
2020-07-06 23:57 ` Jerry Snitselaar
2020-07-07 2:24 ` 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=69907c30-62c2-b4bd-e84f-11612bba9c95@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
/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).