From: Joe Perches <joe@perches.com>
To: linux-kernel@vger.kernel.org
Cc: Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux@vger.kernel.org, Joe Perches <joe@perches.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Kees Cook <keescook@chromium.org>
Subject: Bad file pattern in MAINTAINERS section 'SELINUX SECURITY MODULE'
Date: Mon, 25 Mar 2019 14:27:55 -0700 [thread overview]
Message-ID: <20190325212756.27603-1-joe@perches.com> (raw)
In-Reply-To: <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
A file pattern line in this section of the MAINTAINERS file in linux-next
does not have a match in the linux source files.
This could occur because a matching filename was never added, was deleted
or renamed in some other commit.
The commits that added and if found renamed or removed the file pattern
are shown below.
Please fix this defect appropriately.
1: ---------------------------------------------------------------------------
linux-next MAINTAINERS section:
13949 SELINUX SECURITY MODULE
13950 M: Paul Moore <paul@paul-moore.com>
13951 M: Stephen Smalley <sds@tycho.nsa.gov>
13952 M: Eric Paris <eparis@parisplace.org>
13953 L: selinux@vger.kernel.org
13954 W: https://selinuxproject.org
13955 W: https://github.com/SELinuxProject
13956 T: git git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
13957 S: Supported
--> 13958 F: include/linux/selinux*
13959 F: security/selinux/
13960 F: scripts/selinux/
13961 F: Documentation/admin-guide/LSM/SELinux.rst
2: ---------------------------------------------------------------------------
The most recent commit that added or modified file pattern 'include/linux/selinux*':
commit 679655daffdd2725b66ba2c5a759bbcb316fca5a
Author: Joe Perches <joe@perches.com>
Date: Tue Apr 7 20:44:32 2009 -0700
MAINTAINERS - Add file patterns
Better description of file pattern tag "F:"
Add file exclusion tag "X:"
Add patterns to sections
Signed-off-by: Joe Perches <joe@perches.com>
MAINTAINERS | 1194 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 1193 insertions(+), 1 deletion(-)
3: ---------------------------------------------------------------------------
The last commit with a real presence of file pattern 'include/linux/selinux*':
commit 3d252529480c68bfd6a6774652df7c8968b28e41
Author: Casey Schaufler <casey@schaufler-ca.com>
Date: Fri Sep 21 17:17:34 2018 -0700
SELinux: Remove unused selinux_is_enabled
There are no longer users of selinux_is_enabled().
Remove it. As selinux_is_enabled() is the only reason
for include/linux/selinux.h remove that as well.
Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Kees Cook <keescook@chromium.org>
include/linux/cred.h | 1 -
include/linux/selinux.h | 35 -----------------------------------
security/selinux/Makefile | 2 +-
security/selinux/exports.c | 23 -----------------------
security/selinux/hooks.c | 1 -
security/selinux/include/audit.h | 3 ---
security/selinux/ss/services.c | 1 -
7 files changed, 1 insertion(+), 65 deletions(-)
next parent reply other threads:[~2019-03-25 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7cd8d12f59bcacd18a78f599b46dac555f7f16c0.camel@perches.com>
2019-03-25 21:27 ` Joe Perches [this message]
2019-03-25 21:58 ` [PATCH] Bad file pattern in MAINTAINERS section 'SELINUX SECURITY MODULE' Casey Schaufler
2019-03-25 22:02 ` Joe Perches
2019-03-25 22:22 ` Casey Schaufler
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=20190325212756.27603-1-joe@perches.com \
--to=joe@perches.com \
--cc=casey@schaufler-ca.com \
--cc=eparis@parisplace.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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).