From: Cyril Hrubis <chrubis@suse.cz>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it, Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org, selinux@vger.kernel.org,
Coiby Xu <coxu@redhat.com>
Subject: Re: [PATCH 1/2] ima_policy.sh: Optimize check for policy writable
Date: Mon, 15 Sep 2025 13:55:47 +0200 [thread overview]
Message-ID: <aMf-w-2UtBe3VMZb@yuki.lan> (raw)
In-Reply-To: <20250912073210.47637-2-pvorel@suse.cz>
Hi!
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2025-09-15 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 7:32 [PATCH 0/2] LTP IMA pre-release fixes Petr Vorel
2025-09-12 7:32 ` [PATCH 1/2] ima_policy.sh: Optimize check for policy writable Petr Vorel
2025-09-12 13:18 ` Mimi Zohar
2025-09-15 8:10 ` [LTP] " Avinesh Kumar
2025-09-15 11:55 ` Cyril Hrubis [this message]
2025-09-12 7:32 ` [PATCH 2/2] ima_{conditionals,policy}: Handle policy required to be signed Petr Vorel
2025-09-12 13:23 ` Mimi Zohar
2025-09-16 16:41 ` Petr Vorel
2025-09-15 12:12 ` Cyril Hrubis
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=aMf-w-2UtBe3VMZb@yuki.lan \
--to=chrubis@suse.cz \
--cc=coxu@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=selinux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).