[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ee7408412dd3e1725ae9ef0eeb26e4a4.paul@paul-moore.com>
Date: Tue, 18 Jul 2023 18:01:29 -0400
From: Paul Moore <paul@...l-moore.com>
To: Christian Göttsche <cgzones@...glemail.com>,
selinux@...r.kernel.org
Cc: Stephen Smalley <stephen.smalley.work@...il.com>,
Eric Paris <eparis@...isplace.org>,
Ondrej Mosnacek <omosnace@...hat.com>,
Xiu Jianfeng <xiujianfeng@...weicloud.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 19/20] selinux: status: avoid implicit conversions regarding enforcing status
On Jul 6, 2023 =?UTF-8?q?Christian=20G=C3=B6ttsche?= <cgzones@...glemail.com> wrote:
>
> Use the type bool as parameter type in
> selinux_status_update_setenforce(). The related function
> enforcing_enabled() returns the type bool, while the struct
> selinux_kernel_status member enforcing uses an u32.
>
> Signed-off-by: Christian Göttsche <cgzones@...glemail.com>
> ---
> security/selinux/include/security.h | 2 +-
> security/selinux/selinuxfs.c | 7 ++++---
> security/selinux/status.c | 4 ++--
> 3 files changed, 7 insertions(+), 6 deletions(-)
Merged into selinux/next, thanks.
--
paul-moore.com
Powered by blists - more mailing lists