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 patches for v4.20
Date: Mon, 22 Oct 2018 20:54:50 -0400 [thread overview]
Message-ID: <CAHC9VhRHCOZL5WTwiyPQxknO2SAHCeDLuSJmkKWmYLYb4WFXng@mail.gmail.com> (raw)
Hi Linus,
Welcome back.
Three SELinux patches for v4.20, all fall under the bug-fix or
behave-better category, which is good. All three have pretty good
descriptions too, which is even better. Please merge this for v4.20.
Thanks,
-Paul
--
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20181022
for you to fetch changes up to 4458bba09788e70e8fb39ad003f087cd9dfbd6ac:
selinux: Add __GFP_NOWARN to allocation at str_read()
(2018-09-13 15:36:25 -0400)
----------------------------------------------------------------
selinux/stable-4.20 PR 20181022
----------------------------------------------------------------
Jann Horn (1):
selinux: refactor mls_context_to_sid() and make it stricter
Stephen Smalley (1):
selinux: fix mounting of cgroup2 under older policies
Tetsuo Handa (1):
selinux: Add __GFP_NOWARN to allocation at str_read()
security/selinux/hooks.c | 5 ++
security/selinux/ss/mls.c | 178 ++++++++++++++++++-----------------------
security/selinux/ss/mls.h | 2 +-
security/selinux/ss/policydb.c | 2 +-
security/selinux/ss/services.c | 12 +--
5 files changed, 88 insertions(+), 111 deletions(-)
--
paul moore
www.paul-moore.com
next reply other threads:[~2018-10-23 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 0:54 Paul Moore [this message]
2018-10-24 10:48 ` [GIT PULL] SELinux patches for v4.20 Linus Torvalds
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=CAHC9VhRHCOZL5WTwiyPQxknO2SAHCeDLuSJmkKWmYLYb4WFXng@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).