From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-integrity@vger.kernel.org, ltp@lists.linux.it
Cc: Stefan Berger <stefanb@linux.ibm.com>
Subject: [LTP] [RFC PATCH 1/3] Update validate() to support multiple violations
Date: Thu, 20 Feb 2025 11:00:52 -0500 [thread overview]
Message-ID: <20250220160054.12149-1-zohar@linux.ibm.com> (raw)
Add support for the number of expected violations. Include the
expected number of violations in the output.
Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
---
.../security/integrity/ima/tests/ima_violations.sh | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/testcases/kernel/security/integrity/ima/tests/ima_violations.sh b/testcases/kernel/security/integrity/ima/tests/ima_violations.sh
index 37d8d473c..7f0382fb8 100755
--- a/testcases/kernel/security/integrity/ima/tests/ima_violations.sh
+++ b/testcases/kernel/security/integrity/ima/tests/ima_violations.sh
@@ -71,20 +71,26 @@ validate()
local num_violations="$1"
local count="$2"
local search="$3"
+ local expected_violations=$4
local max_attempt=3
local count2 i num_violations_new
+ [ -z $expected_violations ] && expected_violations=1
+
for i in $(seq 1 $max_attempt); do
read num_violations_new < $IMA_VIOLATIONS
count2="$(get_count $search)"
- if [ $(($num_violations_new - $num_violations)) -gt 0 ]; then
+ if [ $(($num_violations_new - $num_violations)) -eq $expected_violations ]; then
if [ $count2 -gt $count ]; then
- tst_res TPASS "$search violation added"
+ tst_res TPASS "$expected_violations $search violation(s) added"
return
else
tst_res TINFO "$search not found in $LOG ($i/$max_attempt attempt)..."
tst_sleep 1s
fi
+ elif [ $(($num_violations_new - $num_violations)) -gt 0 ]; then
+ tst_res $IMA_FAIL "$search too many violations added"
+ return
else
tst_res $IMA_FAIL "$search violation not added"
return
--
2.48.1
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2025-02-20 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 16:00 Mimi Zohar [this message]
2025-02-20 16:00 ` [LTP] [RFC PATCH 2/3] ima: additional open-writer violation tests Mimi Zohar
2025-02-20 19:02 ` Petr Vorel
2025-02-20 16:00 ` [LTP] [RFC PATCH 3/3] ima: additional ToMToU " Mimi Zohar
2025-02-20 18:16 ` Petr Vorel
2025-02-20 18:46 ` Petr Vorel
2025-02-20 21:15 ` Mimi Zohar
2025-02-20 18:59 ` Mimi Zohar
2025-02-20 19:13 ` Petr Vorel
2025-02-20 20:22 ` Mimi Zohar
2025-02-20 21:18 ` Mimi Zohar
2025-02-20 21:43 ` Petr Vorel
2025-02-21 2:07 ` Mimi Zohar
2025-02-21 8:16 ` Petr Vorel
2025-02-24 18:48 ` Mimi Zohar
2025-02-25 7:45 ` Petr Vorel
2025-02-20 18:50 ` [LTP] [RFC PATCH 1/3] Update validate() to support multiple violations Petr Vorel
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=20250220160054.12149-1-zohar@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=stefanb@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