From: john.johansen@canonical.com (John Johansen)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] apparmor updates for v4.19
Date: Thu, 23 Aug 2018 19:34:46 -0700 [thread overview]
Message-ID: <f4d603ba-254b-fbf5-8d06-11cc61d29de0@canonical.com> (raw)
Hi,
Please pull these apparmor changes for v4.19. There is nothing major this time just 4 bug fixes and a patch to remove so dead code.
Thanks!
- John
The following changes since commit fb7d1bcf1602b46f37ada72178516c01a250e434:
Merge tag 'pci-v4.18-fixes-3' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci (2018-07-19 11:54:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2018-08-23
for you to fetch changes up to c037bd615885f1d9d3bdb48531bace79fae1505d:
apparmor: remove no-op permission check in policy_unpack (2018-08-22 18:44:42 -0700)
----------------------------------------------------------------
+ Cleanups
- apparmor: remove no-op permission check in policy_unpack
+ Bug fixes
- apparmor: fix an error code in __aa_create_ns()
- apparmor: Fix failure to audit context info in build_change_hat
- apparmor: Check buffer bounds when mapping permissions mask
- apparmor: Fully initialize aa_perms struct when answering userspace query
----------------------------------------------------------------
Dan Carpenter (1):
apparmor: fix an error code in __aa_create_ns()
John Johansen (2):
apparmor: Fix failure to audit context info in build_change_hat
apparmor: remove no-op permission check in policy_unpack
Tyler Hicks (2):
apparmor: Check buffer bounds when mapping permissions mask
apparmor: Fully initialize aa_perms struct when answering userspace query
security/apparmor/apparmorfs.c | 5 +----
security/apparmor/domain.c | 2 +-
security/apparmor/file.c | 3 ++-
security/apparmor/include/perms.h | 3 ++-
security/apparmor/lib.c | 17 +++++++++++++----
security/apparmor/policy_ns.c | 2 +-
security/apparmor/policy_unpack.c | 32 --------------------------------
7 files changed, 20 insertions(+), 44 deletions(-)
reply other threads:[~2018-08-24 2:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f4d603ba-254b-fbf5-8d06-11cc61d29de0@canonical.com \
--to=john.johansen@canonical.com \
--cc=linux-security-module@vger.kernel.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).