From: linuxtestproject.agent@gmail.com
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] ima_tpm.sh: update test2 to detect integrity violations
Date: Fri, 14 Aug 2026 14:52:10 +0000 [thread overview]
Message-ID: <20260814145210.3861-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260814135704.1247403-1-zohar@linux.ibm.com>
Hi Mimi,
On Fri, Aug 14, 2026, Mimi Zohar wrote:
> ima_tpm.sh: update test2 to detect integrity violations
> + if [ "$num_violations" -eq 0 ]; then
> + $cmd > hash.txt 2>&1
> + ret=$?
> + else
> + tst_res TINFO "ignoring $num_violations violations"
> cmd="$cmd --ignore-violations"
Could the failure path of the unflagged invocation retain a retry with
--ignore-violations?
The counter read races with new IMA violations. If another task triggers a
ToMToU or open_writers violation after the counter is read as zero but before
evmctl reads the PCRs, the kernel appends a zero-digest record and extends the
PCR with 0xff. This invocation processes that record without
--ignore-violations, extends zeroes instead, and reports a spurious PCR
mismatch. The removed fallback covered this window.
Verdict - Needs revision
---
Note:
The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.
Regards,
LTP AI Reviewer
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-08-14 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 13:57 [PATCH] ima_tpm.sh: update test2 to detect integrity violations Mimi Zohar
2026-08-14 13:57 ` [LTP] " Mimi Zohar
2026-08-14 14:52 ` linuxtestproject.agent [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=20260814145210.3861-1-linuxtestproject.agent@gmail.com \
--to=linuxtestproject.agent@gmail.com \
--cc=ltp@lists.linux.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.