From: Micah Morton <mortonm@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: [GIT PULL] SafeSetID LSM changes for 5.4
Date: Wed, 18 Sep 2019 10:41:06 -0700 [thread overview]
Message-ID: <CAJ-EccM49yBA+xgkR+3m5pEAJqmH_+FxfuAjijrQxaxxMUAt3Q@mail.gmail.com> (raw)
The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
are available in the Git repository at:
https://github.com/micah-morton/linux.git tags/safesetid-bugfix-5.4
for you to fetch changes up to 21ab8580b383f27b7f59b84ac1699cb26d6c3d69:
LSM: SafeSetID: Stop releasing uninitialized ruleset (2019-09-17
11:27:05 -0700)
----------------------------------------------------------------
Fix for SafeSetID bug that was introduced in 5.3
Jann Horn sent some patches to fix some bugs in SafeSetID for 5.3. After
he had done his testing there were a couple small code tweaks that went
in and caused this bug. From what I can see SafeSetID is broken in 5.3
and crashes the kernel every time during initialization if you try to
use it. I came across this bug when backporting Jann's changes for 5.3
to older kernels (4.14 and 4.19). I've tested on a Chrome OS device and
verified that this change fixes things. Unless I'm missing something it
doesn't seem super useful to have this change bake in linux-next, since it is
completely broken in 5.3 and nobody noticed.
Signed-off-by: Micah Morton <mortonm@chromium.org>
----------------------------------------------------------------
Micah Morton (1):
LSM: SafeSetID: Stop releasing uninitialized ruleset
security/safesetid/securityfs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2019-09-18 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 17:41 Micah Morton [this message]
2019-09-23 19:01 ` [GIT PULL] SafeSetID LSM changes for 5.4 Linus Torvalds
2019-09-23 19:28 ` Linus Torvalds
2019-09-23 23:35 ` James Morris
2019-09-24 0:45 ` Linus Torvalds
2019-09-24 3:30 ` Micah Morton
2019-09-26 18:21 ` Linus Torvalds
2019-09-23 23:30 ` Paul E. McKenney
2019-09-24 0:44 ` Linus Torvalds
2019-10-21 6:58 ` Ingo Molnar
2019-10-22 2:13 ` Paul E. McKenney
2019-09-23 19:05 ` 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=CAJ-EccM49yBA+xgkR+3m5pEAJqmH_+FxfuAjijrQxaxxMUAt3Q@mail.gmail.com \
--to=mortonm@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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).