[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhR-Xk65iSfZxVvaK+mJoFszxT2E8vF=cus1aAKcB0EgYg@mail.gmail.com>
Date: Tue, 3 May 2022 16:02:34 -0400
From: Paul Moore <paul@...l-moore.com>
To: Christian Göttsche <cgzones@...glemail.com>
Cc: Casey Schaufler <casey@...aufler-ca.com>,
SElinux list <selinux@...r.kernel.org>,
James Morris <jmorris@...ei.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Xin Long <lucien.xin@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Ondrej Mosnacek <omosnace@...hat.com>,
Mickaël Salaün <mic@...ux.microsoft.com>,
Todd Kjos <tkjos@...gle.com>,
Olga Kornievskaia <kolga@...app.com>,
Linux kernel mailing list <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH] security: declare member holding string literal const
On Mon, May 2, 2022 at 9:38 AM Christian Göttsche
<cgzones@...glemail.com> wrote:
> On Thu, 17 Feb 2022 at 23:50, Casey Schaufler <casey@...aufler-ca.com> wrote:
> > On 2/17/2022 6:18 AM, Christian Göttsche wrote:
> > > The struct security_hook_list member lsm is assigned in
> > > security_add_hooks() with string literals passed from the individual
> > > security modules. Declare the function parameter and the struct member
> > > const to signal their immutability.
> > >
> > > Reported by Clang [-Wwrite-strings]:
> > >
> > > security/selinux/hooks.c:7388:63: error: passing 'const char [8]' to parameter of type 'char *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
> > > security_add_hooks(selinux_hooks, ARRAY_SIZE(selinux_hooks), selinux);
> > > ^~~~~~~~~
> > > ./include/linux/lsm_hooks.h:1629:11: note: passing argument to parameter 'lsm' here
> > > char *lsm);
> > > ^
> > >
> > > Signed-off-by: Christian Göttsche <cgzones@...glemail.com>
> >
> > Reviewed-by: Casey Schaufler <casey@...aufler-ca.com>
> >
>
> Kindly ping;
> any progress on this one?
I've already added my Reviewed-by tag, as has Casey, so I think it's
pretty "safe" at this point. The next step is for James to pull this
into the LSM tree. If it is still collecting dust at the end of this
week, ping us again and I can just go ahead and pull it into the
SELinux tree, it's small enough that it shouldn't cause any problems.
--
paul-moore.com
Powered by blists - more mailing lists