From: "Andrea Cervesato" <andrea.cervesato@suse.com>
To: "Petr Vorel" <pvorel@suse.cz>,
"Andrea Cervesato" <andrea.cervesato@suse.com>
Cc: <ltp@lists.linux.it>, <linux-integrity@vger.kernel.org>
Subject: Re: [LTP] [PATCH 2/4] ima_conditionals.sh: Split test by request
Date: Mon, 06 Oct 2025 13:40:09 +0200 [thread overview]
Message-ID: <DDB7LLBEXIQM.2KSWEVEFU0TVS@suse.com> (raw)
In-Reply-To: <20251006112136.GA82874@pevik>
> verify_measurement() writes into /sys/kernel/security/ima/policy which on
> kernels without CONFIG_IMA_WRITE_POLICY requires SUT reboot. Because LTP does
> not support any reboot, this needs to be handled after test finishes. That's why
> I separated the tests. This helps to cover more than the first test case out of
> four.
Now I see, this is clearly a corner case given by LTP limitations. I
think we should probably start to think about reboot flag then. Once the
PR for the new SUT will be implemented in kirk, it's time to work on
this.
--
Andrea Cervesato
andrea.cervesato@suse.com
next prev parent reply other threads:[~2025-10-06 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 8:36 [PATCH 0/4] ima_{conditionals,measurements}.sh enhancements Petr Vorel
2025-10-02 8:36 ` [PATCH 1/4] ima_{conditionals,measurements}.sh: Add temporary user Petr Vorel
2025-10-02 8:36 ` [PATCH 2/4] ima_conditionals.sh: Split test by request Petr Vorel
2025-10-06 7:26 ` [LTP] " Andrea Cervesato
2025-10-06 11:21 ` Petr Vorel
2025-10-06 11:40 ` Andrea Cervesato [this message]
2025-10-08 4:38 ` Petr Vorel
2025-10-02 8:37 ` [PATCH 3/4] ima_conditionals.sh: Use 'sg' without 'sudo' Petr Vorel
2025-10-02 8:37 ` [PATCH 4/4] ima_{conditionals,measurements}.sh: Use 'su' instead of 'sudo' Petr Vorel
2025-10-06 7:26 ` [LTP] [PATCH 0/4] ima_{conditionals,measurements}.sh enhancements Andrea Cervesato
2025-10-06 9:35 ` 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=DDB7LLBEXIQM.2KSWEVEFU0TVS@suse.com \
--to=andrea.cervesato@suse.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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).