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.7 (#2)
Date: Thu, 30 Apr 2020 17:24:20 -0400 [thread overview]
Message-ID: <CAHC9VhTu3YWPmwtA7RERHDRhQt0wAkmN4GJCmaRY7KSFRwtACQ@mail.gmail.com> (raw)
Hi Linus,
Two more SELinux patches to fix problems in the v5.7-rcX releases.
Wei Yongjun's patch fixes a return code in an error path, and my patch
fixes a problem where we were not correctly applying access controls
to all of the netlink messages in the netlink_send LSM hook. Both
patches pass our tests without problem and currently apply cleanly on
top of your master branch. Please merge for the next -rcX release.
Thanks,
-Paul
--
The following changes since commit af15f14c8cfcee515f4e9078889045ad63efefe3:
selinux: free str on error in str_read() (2020-04-15 17:23:16 -0400)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
tags/selinux-pr-20200430
for you to fetch changes up to fb73974172ffaaf57a7c42f35424d9aece1a5af6:
selinux: properly handle multiple messages in selinux_netlink_send()
(2020-04-30 16:18:37 -0400)
----------------------------------------------------------------
selinux/stable-5.7 PR 20200430
----------------------------------------------------------------
Paul Moore (1):
selinux: properly handle multiple messages in selinux_netlink_send()
Wei Yongjun (1):
selinux: fix error return code in cond_read_list()
security/selinux/hooks.c | 70 +++++++++++++++++++++----------
security/selinux/ss/conditional.c | 2 +-
2 files changed, 46 insertions(+), 26 deletions(-)
--
paul moore
www.paul-moore.com
next reply other threads:[~2020-04-30 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 21:24 Paul Moore [this message]
2020-04-30 23:43 ` [GIT PULL] SELinux fixes for v5.7 (#2) Linus Torvalds
2020-05-01 16:17 ` Paul Moore
2020-04-30 23:50 ` 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=CAHC9VhTu3YWPmwtA7RERHDRhQt0wAkmN4GJCmaRY7KSFRwtACQ@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).