From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] SELinux fixes for v5.1 (#3)
Date: Mon, 29 Apr 2019 18:55:19 -0400 [thread overview]
Message-ID: <CAHC9VhQ6QF7LvuFjr2YdYNX-3pW80nm+VJh4jK080JsKOzOVsA@mail.gmail.com> (raw)
Hi Linus,
One small patch for the stable folks to fix a problem when building
against the latest glibc. I'll be honest and say that I'm not really
thrilled with the idea of sending this up right now, but Greg is a
little annoyed so here I figured I would at least send the PR.
-Paul
--
The following changes since commit 6a1afffb08ce5f9fb9ccc20f7ab24846c0142984:
selinux: fix NULL dereference in policydb_destroy()
(2019-03-18 12:19:48 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20190429
for you to fetch changes up to dfbd199a7cfe3e3cd8531e1353cdbd7175bfbc5e:
selinux: use kernel linux/socket.h for genheaders and mdp
(2019-04-29 11:34:58 -0400)
----------------------------------------------------------------
selinux/stable-5.1 PR 20190429
----------------------------------------------------------------
Paulo Alcantara (1):
selinux: use kernel linux/socket.h for genheaders and mdp
scripts/selinux/genheaders/genheaders.c | 1 -
scripts/selinux/mdp/mdp.c | 1 -
security/selinux/include/classmap.h | 1 +
3 files changed, 1 insertion(+), 2 deletions(-)
--
paul moore
www.paul-moore.com
next reply other threads:[~2019-04-29 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 22:55 Paul Moore [this message]
2019-04-30 18:25 ` [GIT PULL] SELinux fixes for v5.1 (#3) pr-tracker-bot
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=CAHC9VhQ6QF7LvuFjr2YdYNX-3pW80nm+VJh4jK080JsKOzOVsA@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=selinux@vger.kernel.org \
--cc=torvalds@linux-foundation.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).