From: John Johansen <john.johansen@canonical.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKLM <linux-kernel@vger.kernel.org>,
"open list:SECURITY SUBSYSTEM"
<linux-security-module@vger.kernel.org>
Subject: [GIT PULL] apparmor bug fixes for v5.5-rc5
Date: Sat, 4 Jan 2020 17:36:48 -0800 [thread overview]
Message-ID: <cbec7335-39b8-6b7d-402b-a6dd467b492b@canonical.com> (raw)
Hi Linus,
Can you please pull the following bug fixes for apparmor
Thanks!
- John
The following changes since commit fd6988496e79a6a4bdb514a4655d2920209eb85d:
Linux 5.5-rc4 (2019-12-29 15:29:16 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2020-01-04
for you to fetch changes up to 8c62ed27a12c00e3db1c9f04bc0f272bdbb06734:
apparmor: fix aa_xattrs_match() may sleep while holding a RCU lock (2020-01-04 15:56:44 -0800)
----------------------------------------------------------------
+ Bug fixes
- performance regression: only get a label reference if the fast
path check fails
- fix aa_xattrs_match() may sleep while holding a RCU lock
- fix bind mounts aborting with -ENOMEM
----------------------------------------------------------------
John Johansen (2):
apparmor: only get a label reference if the fast path check fails
apparmor: fix aa_xattrs_match() may sleep while holding a RCU lock
Patrick Steinhardt (1):
apparmor: fix bind mounts aborting with -ENOMEM
security/apparmor/apparmorfs.c | 2 +-
security/apparmor/domain.c | 82 ++++++++++++++++++++++--------------------
security/apparmor/file.c | 12 ++++---
security/apparmor/mount.c | 2 +-
security/apparmor/policy.c | 4 +--
5 files changed, 55 insertions(+), 47 deletions(-)
next reply other threads:[~2020-01-05 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 1:36 John Johansen [this message]
2020-01-05 3:35 ` [GIT PULL] apparmor bug fixes for v5.5-rc5 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=cbec7335-39b8-6b7d-402b-a6dd467b492b@canonical.com \
--to=john.johansen@canonical.com \
--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).