From: Bruno Meneguele <bmeneg@redhat.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: Petr Vorel <pvorel@suse.cz>,
ltp@lists.linux.it, Mimi Zohar <zohar@linux.vnet.ibm.com>,
Petr Cervinka <pcervinka@suse.com>,
Cyril Hrubis <chrubis@suse.cz>,
linux-integrity@vger.kernel.org,
Vitaly Chikunov <vt@altlinux.org>
Subject: Re: [LTP v2 1/1] ima_tpm.sh: Fix for calculating boot aggregate
Date: Wed, 17 Jun 2020 16:52:05 -0300 [thread overview]
Message-ID: <20200617195205.GA40831@glitch> (raw)
In-Reply-To: <1592347211.11061.250.camel@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
On Tue, Jun 16, 2020 at 06:40:11PM -0400, Mimi Zohar wrote:
> On Mon, 2020-06-15 at 17:01 -0300, Bruno Meneguele wrote:
> > On Mon, Jun 15, 2020 at 04:41:34PM -0300, Bruno Meneguele wrote:
> > > On Thu, May 28, 2020 at 06:05:27PM +0200, Petr Vorel wrote:
>
> > > > > The boot_aggregate.trs and boot_aggregate.log files are being created
> > > > > in the tests/ directory. Is that directory read-only?
> > > > Yes, drwxr-xr-x. Testing on fresh clone and issue persists.
> > > >
> > >
> > > Yes, same thing here.. but didn't really check the reason for that. Will
> > > take a time later to see what's happening.
>
> Cloning as root will cause that to happen.
>
> $ sudo git clone git://git.code.sf.net/p/linux-ima/ima-evm-utils --branch next-testing
> Cloning into 'ima-evm-utils'...
> remote: Enumerating objects: 1154, done.
> remote: Counting objects: 100% (1154/1154), done.
> remote: Compressing objects: 100% (1052/1052), done.
> remote: Total 1154 (delta 736), reused 182 (delta 96)
> Receiving objects: 100% (1154/1154), 335.12 KiB | 0 bytes/s, done.
> Resolving deltas: 100% (736/736), done.
> Checking connectivity... done.
>
> $ ls -lat ima-evm-utils/ | grep tests
> drwxr-xr-x. 2 root root 220 Jun 16 18:28 tests
>
> Mimi
>
Yes, indeed. But what really happened with both I and Petr was trying to
run the test copying and pasting what you've sent:
$ VERBOSE=1 make check TESTS=boog_aggregate.test
the typo in "boog" (vs "boot") was the cause. So I think we can ignore
this issue here :).
--
bmeneg
PGP Key: http://bmeneg.com/pubkey.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-17 19:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 7:14 [LTP v2 1/1] ima_tpm.sh: Fix for calculating boot aggregate Petr Vorel
2020-05-27 17:41 ` Mimi Zohar
2020-05-28 14:07 ` Petr Vorel
2020-05-28 15:19 ` Mimi Zohar
2020-05-28 16:05 ` Petr Vorel
2020-06-15 19:41 ` Bruno Meneguele
2020-06-15 20:01 ` Bruno Meneguele
2020-06-16 22:40 ` Mimi Zohar
2020-06-17 19:52 ` Bruno Meneguele [this message]
2020-06-19 7:46 ` Petr Vorel
2020-06-15 20:21 ` Mimi Zohar
2020-06-17 1:21 ` Jerry Snitselaar
2020-06-17 20:45 ` Bruno Meneguele
2020-06-17 22:19 ` Maurizio Drocco
2020-06-19 8:21 ` Petr Vorel
2020-06-19 12:43 ` Mimi Zohar
2020-06-19 13:01 ` Petr Vorel
2020-06-19 10:07 ` Petr Vorel
2020-06-19 13:01 ` Mimi Zohar
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=20200617195205.GA40831@glitch \
--to=bmeneg@redhat.com \
--cc=chrubis@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pcervinka@suse.com \
--cc=pvorel@suse.cz \
--cc=vt@altlinux.org \
--cc=zohar@linux.ibm.com \
--cc=zohar@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).