From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: Richard Haines <richard_c_haines@btinternet.com>,
SElinux list <selinux@vger.kernel.org>,
Stephen Smalley <stephen.smalley.work@gmail.com>,
Eric Paris <eparis@parisplace.org>,
demiobenour@gmail.com,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
selinux-refpolicy@vger.kernel.org,
Jeff Vander Stoep <jeffv@google.com>
Subject: Re: [PATCH V3] security/selinux: Always allow FIOCLEX and FIONCLEX
Date: Fri, 25 Feb 2022 15:54:46 -0500 [thread overview]
Message-ID: <CAHC9VhTW+zZQb6a2QE2iRYfyyUxjMphRYfSWt6bgp2JvodrTgQ@mail.gmail.com> (raw)
In-Reply-To: <CAFqZXNtLw_c1V7MvQ=uVO9da1LH0dP64Vy3eEvL8Por_o6NQ5A@mail.gmail.com>
On Fri, Feb 25, 2022 at 5:02 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> (IMHO the POLICYDB_CAPABILITY_ prefix is ridiculously long for no
> reason and we should simply shorten it (just POLCAP_ would be
> perfectly fine, IMHO) instead of trying to abbreviate the rest. Of
> course, this doesn't have to be done now - I'm taking a note to myself
> to splice in such rename next time I add a new capability, if not
> earlier.)
Yeah, that prefix is probably longer than it needs to be. Since we're
at -rc5 right now, with -rc6 just a few days away, I'll go ahead and
toss out a patch to shorten the names next week. While I have very
mixed feelings on style/formatting-only patches, things like this
should go into selinux/next at the end of the -rcX cycle so as not to
cause unnecessary conflicts for people making "real" changes :)
--
paul-moore.com
prev parent reply other threads:[~2022-02-25 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:24 [PATCH V3] security/selinux: Always allow FIOCLEX and FIONCLEX Richard Haines
2022-02-25 0:34 ` Paul Moore
2022-02-25 10:01 ` Ondrej Mosnacek
2022-02-25 20:54 ` Paul Moore [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=CAHC9VhTW+zZQb6a2QE2iRYfyyUxjMphRYfSWt6bgp2JvodrTgQ@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=demiobenour@gmail.com \
--cc=eparis@parisplace.org \
--cc=jeffv@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux-refpolicy@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).