[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e482fa5c364bfc58aebc938a4c07e61f0fe71c88.camel@linux.ibm.com>
Date: Fri, 10 Mar 2023 08:30:21 -0500
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Roberto Sassu <roberto.sassu@...weicloud.com>,
dmitry.kasatkin@...il.com, paul@...l-moore.com, jmorris@...ei.org,
serge@...lyn.com, mic@...ikod.net
Cc: linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, bpf@...r.kernel.org,
linux-kernel@...r.kernel.org, keescook@...omium.org,
Roberto Sassu <roberto.sassu@...wei.com>
Subject: Re: [PATCH v4 2/3] Revert "integrity: double check iint_cache was
initialized"
On Fri, 2023-03-10 at 09:54 +0100, Roberto Sassu wrote:
> From: Roberto Sassu <roberto.sassu@...wei.com>
>
> With the recent introduction of LSM_ORDER_LAST, the 'integrity' LSM is
> always initialized (if selected in the kernel configuration) and the
> iint_cache is always created (the kernel panics on error). Thus, the
> additional check of iint_cache in integrity_inode_get() is no longer
> necessary. If the 'integrity' LSM is not selected in the kernel
> configuration, integrity_inode_get() just returns NULL.
>
> This reverts commit 92063f3ca73aab794bd5408d3361fd5b5ea33079.
>
> Signed-off-by: Roberto Sassu <roberto.sassu@...wei.com>
Acked-by: Mimi Zohar <zohar@...ux.ibm.com>
Powered by blists - more mailing lists