From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Roberto Sassu" <roberto.sassu@huaweicloud.com>, <corbet@lwn.net>,
<zohar@linux.ibm.com>, <dmitry.kasatkin@gmail.com>,
<eric.snowberg@oracle.com>, <paul@paul-moore.com>,
<jmorris@namei.org>, <serge@hallyn.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-integrity@vger.kernel.org>,
<linux-security-module@vger.kernel.org>,
<wufan@linux.microsoft.com>, <pbrobinson@gmail.com>,
<zbyszek@in.waw.pl>, <hch@lst.de>, <mjg59@srcf.ucam.org>,
<pmatilai@redhat.com>, <jannh@google.com>, <dhowells@redhat.com>,
<jikos@kernel.org>, <mkoutny@suse.com>, <ppavlu@suse.com>,
<petr.vorel@gmail.com>, <mzerqung@0pointer.de>,
<kgold@linux.ibm.com>, "Roberto Sassu" <roberto.sassu@huawei.com>
Subject: Re: [RFC][PATCH v3 01/10] ima: Introduce hook DIGEST_LIST_CHECK
Date: Fri, 06 Sep 2024 16:40:06 +0300 [thread overview]
Message-ID: <D3Z8S9922SIU.QD22EOW9RGT0@kernel.org> (raw)
In-Reply-To: <81fd98ce8a43c209e909144a13dcdbf3239e15ff.camel@huaweicloud.com>
On Fri Sep 6, 2024 at 2:22 PM EEST, Roberto Sassu wrote:
> On Fri, 2024-09-06 at 12:41 +0300, Jarkko Sakkinen wrote:
> > On Thu Sep 5, 2024 at 6:25 PM EEST, Roberto Sassu wrote:
> > > From: Roberto Sassu <roberto.sassu@huawei.com>
> > >
> > > Introduce a new hook to check the integrity of digest lists.
> >
> > "Introduce DIGEST_LIST_CHECK, a new hook..."
> >
> > >
> > > The new hook is invoked during a kernel read with file type
> >
> > "with the file type"
> >
> >
> > > READING_DIGEST LIST, which is done by the Integrity Digest Cache when it is
> > > populating a digest cache with a digest list.
> >
> > The patch creates a new struct imap_rule_entry instance when it parses
> > the corresponding rule, which means that there are couple slices of
> > information missing here:
> >
> > 1. The commit message does not tell what the code change effectively
> > is. I scavenged this information from [1].
>
> Sorry, to me it seems a bit redundant to state what a IMA hook is. The
> new hook will be handled by IMA like the other existing hooks.
I think with documentation (scoping also to commit messages) it is in
general a good strategy to put it less rather than more. No
documentation is better than polluted documentation ;-)
Just remarking what might not be obvious with someone who might not
be obvious, unless being a pro-active contributor.
BR, Jarkko
next prev parent reply other threads:[~2024-09-06 13:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 15:25 [RFC][PATCH v3 00/10] ima: Integrate with Integrity Digest Cache Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 01/10] ima: Introduce hook DIGEST_LIST_CHECK Roberto Sassu
2024-09-06 9:41 ` Jarkko Sakkinen
2024-09-06 11:22 ` Roberto Sassu
2024-09-06 13:40 ` Jarkko Sakkinen [this message]
2024-09-05 15:25 ` [RFC][PATCH v3 02/10] ima: Nest iint mutex for DIGEST_LIST_CHECK hook Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 03/10] ima: Add digest_cache policy keyword Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 04/10] ima: Add digest_cache_measure/appraise boot-time built-in policies Roberto Sassu
2024-09-06 9:45 ` Jarkko Sakkinen
2024-09-06 11:25 ` Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 05/10] ima: Modify existing boot-time built-in policies with digest cache policies Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 06/10] ima: Retrieve digest cache and check if changed Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 07/10] ima: Store verified usage in digest cache based on integrity metadata flags Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 08/10] ima: Load verified usage from digest cache found from query Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 09/10] ima: Use digest caches for measurement Roberto Sassu
2024-09-05 15:25 ` [RFC][PATCH v3 10/10] ima: Use digest caches for appraisal 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=D3Z8S9922SIU.QD22EOW9RGT0@kernel.org \
--to=jarkko@kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eric.snowberg@oracle.com \
--cc=hch@lst.de \
--cc=jannh@google.com \
--cc=jikos@kernel.org \
--cc=jmorris@namei.org \
--cc=kgold@linux.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mkoutny@suse.com \
--cc=mzerqung@0pointer.de \
--cc=paul@paul-moore.com \
--cc=pbrobinson@gmail.com \
--cc=petr.vorel@gmail.com \
--cc=pmatilai@redhat.com \
--cc=ppavlu@suse.com \
--cc=roberto.sassu@huawei.com \
--cc=roberto.sassu@huaweicloud.com \
--cc=serge@hallyn.com \
--cc=wufan@linux.microsoft.com \
--cc=zbyszek@in.waw.pl \
--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