[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhSzppHevG_Td+hKU4KRSDgV_NYf2RSeKA06PR-rD+dJLw@mail.gmail.com>
Date: Fri, 10 Mar 2023 17:33:41 -0500
From: Paul Moore <paul@...l-moore.com>
To: Mirsad Goran Todorovac <mirsad.goran.todorovac@....hr>
Cc: linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Thomas Weißschuh <linux@...ssschuh.net>,
Mimi Zohar <zohar@...ux.ibm.com>,
Casey Schaufler <casey@...aufler-ca.com>,
Christian Göttsche <cgzones@...glemail.com>,
Mickaël Salaün <mic@...ikod.net>,
Frederick Lawler <fred@...udflare.com>
Subject: Re: [PATCH v1 0/2] Add destructor hook to LSM modules
On Fri, Mar 10, 2023 at 2:26 PM Mirsad Goran Todorovac
<mirsad.goran.todorovac@....hr> wrote:
>
> LSM security/integrity/iint.c had the case of kmem_cache_create() w/o a proper
> kmem_cache_destroy() destructor.
>
> Introducing the release() hook would enable LSMs to release allocated resources
> on exit, and in proper order, rather than dying all together with kernel shutdown
> in an undefined order.
>
> Thanks,
> Mirsad
>
> ---
> include/linux/lsm_hooks.h | 1 +
> security/integrity/iint.c | 7 +++++++
> 2 files changed, 8 insertions(+)
I only see the 1/2 patch, did you send the 2/2 patch to the LSM list?
If not, you need to do that.
--
paul-moore.com
Powered by blists - more mailing lists