Linux Integrity Measurement development
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Roberto Sassu <roberto.sassu@huaweicloud.com>,
	Stefan Berger <stefanb@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org,
	Roberto Sassu <roberto.sassu@huawei.com>,
	Petr Vorel <pvorel@suse.cz>
Subject: Re: [PATCH ima-evm-utils] Add tests for MMAP_CHECK and MMAP_CHECK_REQPROT hooks
Date: Mon, 30 Jan 2023 08:28:03 -0500	[thread overview]
Message-ID: <420799029373c9e0feae4eb21ca27b7253494591.camel@linux.ibm.com> (raw)
In-Reply-To: <36d25da9b9b6aa004311e083a67bc44f3edcf05c.camel@huaweicloud.com>

[Trimmed Cc list, since this is an ima-evm-utils discussion.  Adding
Petr.]

On Fri, 2023-01-27 at 08:57 +0100, Roberto Sassu wrote:
> On Thu, 2023-01-26 at 17:25 -0500, Stefan Berger wrote:

> > How do you tell the user that the patches need to be applied for the test to
> > succeed and not worry about it when the patches are not applied?
> 
> Uhm, I agree. I should at least write a comment as for EVM portable
> signatures, and maybe display a message in the test logs.

This is a generic problem that needs to be addressed.  FYI, LTP
addressed it by introducing "struct test_tag" in commit ca2c76990
("lib: Add support for test tags").

thanks,

Mimi


  reply	other threads:[~2023-01-30 13:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 16:38 [PATCH v3 1/2] ima: Align ima_file_mmap() parameters with mmap_file LSM hook Roberto Sassu
2023-01-26 16:38 ` [PATCH v3 2/2] ima: Introduce MMAP_CHECK_REQPROT hook Roberto Sassu
2023-01-29 14:52   ` Mimi Zohar
2023-01-30 10:37     ` Roberto Sassu
2023-01-26 16:38 ` [PATCH ima-evm-utils] Add tests for MMAP_CHECK and MMAP_CHECK_REQPROT hooks Roberto Sassu
2023-01-26 22:25   ` Stefan Berger
2023-01-27  7:57     ` Roberto Sassu
2023-01-30 13:28       ` Mimi Zohar [this message]
2023-01-30 14:02         ` Roberto Sassu
2023-01-30 16:07           ` Roberto Sassu
2023-01-30 16:54             ` Mimi Zohar
2023-01-30 16:56               ` Roberto Sassu
2023-01-30 16:26           ` Mimi Zohar
2023-01-30 16:36             ` Roberto Sassu
2023-01-30 17:00               ` Mimi Zohar
2023-01-26 19:37 ` [PATCH v3 1/2] ima: Align ima_file_mmap() parameters with mmap_file LSM hook Stefan Berger
2023-01-27  7:55   ` Roberto Sassu

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=420799029373c9e0feae4eb21ca27b7253494591.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=pvorel@suse.cz \
    --cc=roberto.sassu@huawei.com \
    --cc=roberto.sassu@huaweicloud.com \
    --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