From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: David Howells <dhowells@redhat.com>, Petr Vorel <pvorel@suse.cz>,
shuah <shuah@kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-integrity@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test
Date: Tue, 29 Oct 2019 13:49:22 +0200 [thread overview]
Message-ID: <20191029114922.GA12825@linux.intel.com> (raw)
In-Reply-To: <20191029114535.GA12272@linux.intel.com>
On Tue, Oct 29, 2019 at 01:45:35PM +0200, Jarkko Sakkinen wrote:
> On Tue, Oct 29, 2019 at 11:25:16AM +0200, Jarkko Sakkinen wrote:
> > I'll anyway try to setup user space with TrouSerS so that I can try
> > it out. BuildRoot has recipe for that but not for IBM TSS 2.0 so I'll
> > skip that and use my own test script for TPM2 trusted keys.
>
> Busybox version of mktemp gives this error message:
>
> mktemp: Invalid argument
>
> I get that three times.
>
> Then I get non-existent directory error from line 65 but it is probably
> consequence of the previous errors.
>
> This the help for mktemp:
>
> "
> Usage: mktemp [-dt] [-p DIR] [TEMPLATE]
>
> Create a temporary file with name based on TEMPLATE and print its name.
> TEMPLATE must end with XXXXXX (e.g. [/dir/]nameXXXXXX).
> Without TEMPLATE, -t tmp.XXXXXX is assumed.
>
> -d Make directory, not file
> -q Fail silently on errors
> -t Prepend base directory name to TEMPLATE
> -p DIR Use DIR as a base directory (implies -t)
> -u Do not create anything; print a name
>
> Base directory is: -p DIR, else $TMPDIR, else /tmp
> "
>
> Use total six X's seems to fix the problem.
OK, I fixes that issue and then I end up with:
[INFO] add_key: No such device
Anyway, got further.
/Jarkko
prev parent reply other threads:[~2019-10-29 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:14 [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test Mimi Zohar
2019-10-24 19:24 ` Mimi Zohar
2019-10-28 20:35 ` Jarkko Sakkinen
2019-10-28 20:30 ` Jarkko Sakkinen
2019-10-28 20:40 ` Jarkko Sakkinen
2019-10-28 20:45 ` Mimi Zohar
2019-10-29 9:15 ` Jarkko Sakkinen
2019-10-29 9:25 ` Jarkko Sakkinen
2019-10-29 11:45 ` Jarkko Sakkinen
2019-10-29 11:49 ` Jarkko Sakkinen [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=20191029114922.GA12825@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dhowells@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=shuah@kernel.org \
--cc=zohar@linux.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).