From: mka@chromium.org (Matthias Kaehlcke)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] selinux: Mark array 'labeling_behaviors' as __maybe_unused
Date: Fri, 19 May 2017 09:52:59 -0700 [thread overview]
Message-ID: <20170519165259.GJ141096@google.com> (raw)
In-Reply-To: <1495208719.2209.12.camel@tycho.nsa.gov>
El Fri, May 19, 2017 at 11:45:19AM -0400 Stephen Smalley ha dit:
> On Fri, 2017-05-19 at 11:09 -0400, Paul Moore wrote:
> > On Thu, May 18, 2017 at 3:07 PM, Matthias Kaehlcke <mka@chromium.org>
> > wrote:
> > > The array is only referenced in an ARRAY_SIZE() statement. Adding
> > > the
> > > attribute fixes the following warning when building with clang:
> > >
> > > security/selinux/hooks.c:338:20: error: variable
> > > 'labeling_behaviors'
> > > ????is not needed and will not be emitted
> > > ????[-Werror,-Wunneeded-internal-declaration]
> > >
> > > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > > ---
> > > ?security/selinux/hooks.c | 2 +-
> > > ?1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > The fact that we only reference labeling_behaviors in one spot, and
> > even then we only use it as a parameter to ARRAY_SIZE(), makes me
> > believe we may be able to get rid of labeling_behaviors and use
> > SECURITY_FS_USE_MAX in its place.
> >
> > Anyone working on any patches which make use of labeling_behaviors?
>
> I think you could just remove both the array and the code that
> referenced it; it only made sense before commit
> 2088d60e3b2f53d0c9590a0202eeff85b288b1eb. We already check that the
> policy doesn't contain any behavior > SECURITY_FS_USE_MAX during policy
> load, so this cannot occur (modulo memory corruption), and it was only
> there to make sure we didn't try to dereference off the end of the
> array prior to the aforementioned commit.
Thanks for your comments.
I will send out a patch that removes the array shortly.
Matthias
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-05-19 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 19:07 [PATCH] selinux: Mark array 'labeling_behaviors' as __maybe_unused Matthias Kaehlcke
2017-05-19 15:09 ` Paul Moore
2017-05-19 15:45 ` Stephen Smalley
2017-05-19 16:52 ` Matthias Kaehlcke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170519165259.GJ141096@google.com \
--to=mka@chromium.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).