From: Petr Vorel <pvorel@suse.cz>
To: djacobs7@binghamton.edu
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
zohar@linux.ibm.com, vt@altlinux.org
Subject: Re: [PATCH v2 1/8] evmtest: Regression testing integrity subsystem
Date: Fri, 22 Mar 2019 13:18:42 +0100 [thread overview]
Message-ID: <20190322121842.GA32091@dell5510> (raw)
In-Reply-To: <20190322083441.31084-1-djacobs7@binghamton.edu>
Hi David,
> $ evmtest runtest example_test -e /bin/bash
> [*] Starting test: example_test
> [*] TEST: PASSED
> Example 1a: successful verbose example test output
> $ evmtest runtest example_test -e /bin/bash -v
...
> Changelog:
...
> * checkbashishms compliant
Not yet :). I noticed using
source (should be .)
== (should be =)
${BASH_SOURCE[0]} (should be $0)
$UID (should be $(id -u)
bash redirection &>> (should be >/dev/null 2>&1)
+= (should be VAR="${VAR}foo")
and bash shebang.
Could you please fix that?
...
> +++ b/evmtest/evmtest
> @@ -0,0 +1,67 @@
> +#!/bin/bash
Can we, please, use /bin/sh and not-expect bash?
Portability matters.
> +source "$EVMDIR"/files/common.sh
> +usage (){
> + echo "Usage:"
> + echo " evmtest runtest <test name> [OPTIONS]"
> + echo ""
Can be just echo. Maybe using cat might be better than many echos:
cat <<EOF
Usage:
\tevmtest runtest <test name> [OPTIONS]
...
EOF
Kind regards,
Petr
prev parent reply other threads:[~2019-03-22 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 8:34 [PATCH v2 1/8] evmtest: Regression testing integrity subsystem djacobs7
2019-03-22 8:34 ` [PATCH v2 2/8] evmtest: test loading IMA policies djacobs7
2019-03-22 8:34 ` [PATCH v2 3/8] evmtest: test kernel module loading djacobs7
2019-03-22 8:34 ` [PATCH v2 4/8] evmtest: test kexec signature policy djacobs7
2019-03-22 8:34 ` [PATCH v2 5/8] evmtest: validate boot record djacobs7
2019-03-22 8:34 ` [PATCH v2 6/8] evmtest: test the preservation of extended attributes djacobs7
2019-03-22 8:34 ` [PATCH v2 7/8] emvtest: Add ability to run all tests djacobs7
2019-03-22 8:34 ` [PATCH v2 8/8] evmtest: virtual machine compatibility djacobs7
2019-03-22 12:18 ` Petr Vorel [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=20190322121842.GA32091@dell5510 \
--to=pvorel@suse.cz \
--cc=djacobs7@binghamton.edu \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vt@altlinux.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