[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhRo2GzW0jSqmm0Sv3z_-q9PTsvScV5oQwF5uNh+ZcWreA@mail.gmail.com>
Date: Tue, 7 Nov 2023 22:12:24 -0500
From: Paul Moore <paul@...l-moore.com>
To: Ondrej Mosnacek <omosnace@...hat.com>
Cc: linux-security-module@...r.kernel.org,
Benjamin Coddington <bcodding@...hat.com>,
linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] lsm: fix default return values for some hooks
On Tue, Oct 31, 2023 at 8:32 AM Ondrej Mosnacek <omosnace@...hat.com> wrote:
>
> Some of the default return values listed in <linux/lsm_hook_defs.h>
> don't match the actual no-op value and can be trivially fixed.
>
> Ondrej Mosnacek (2):
> lsm: fix default return value for vm_enough_memory
> lsm: fix default return value for inode_getsecctx
>
> include/linux/lsm_hook_defs.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
These both look like reasonable -stable candidates to me, what do you think?
--
paul-moore.com
Powered by blists - more mailing lists