mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 updates for v4.15
Date: Tue, 21 Nov 2017 09:07:44 -0800	[thread overview]
Message-ID: <2d41559d-4a1d-c3fb-252e-54a165e7466c@canonical.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2577 bytes --]

Hi,

No features this time, just minor cleanups and bug fixes.

Please pull these apparmor changes for v4.15

Thanks!

- John


The following changes since commit 0b07194bb55ed836c2cc7c22e866b87a14681984:

  Linux 4.14-rc7 (2017-10-29 13:58:38 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2017-11-21

for you to fetch changes up to feb3c766a3ab32d233aaff7db13afd9ba5bc142d:

  apparmor: fix possible recursive lock warning in __aa_create_ns (2017-11-21 02:17:16 -0800)

----------------------------------------------------------------
+ Cleanups
  - apparmor: fix spelling mistake: "resoure" -> "resource"
  - apparmor: remove unused redundant variable stop
  - apparmor: Fix bool initialization/comparison

+ Bug Fixes
  - apparmor: initialized returned struct aa_perms
  - apparmor: fix leak of null profile name if profile allocation fails
  - apparmor: ensure that undecidable profile attachments fail
  - apparmor: fix profile attachment for special unconfined profiles
  - apparmor: fix locking when creating a new complain profile.
  - apparmor: fix possible recursive lock warning in __aa_create_ns

----------------------------------------------------------------
Arnd Bergmann (1):
      apparmor: initialized returned struct aa_perms

Colin Ian King (2):
      apparmor: fix spelling mistake: "resoure" -> "resource"
      apparmor: remove unused redundant variable stop

John Johansen (5):
      apparmor: fix leak of null profile name if profile allocation fails
      apparmor: ensure that undecidable profile attachments fail
      apparmor: fix profile attachment for special unconfined profiles
      apparmor: fix locking when creating a new complain profile.
      apparmor: fix possible recursive lock warning in __aa_create_ns

Thomas Meyer (1):
      apparmor: Fix bool initialization/comparison

 security/apparmor/apparmorfs.c    | 22 ++++++-------
 security/apparmor/domain.c        | 68 ++++++++++++++++++++++++++++-----------
 security/apparmor/file.c          |  8 +----
 security/apparmor/label.c         |  2 +-
 security/apparmor/lib.c           | 16 +++------
 security/apparmor/lsm.c           |  8 ++---
 security/apparmor/mount.c         | 13 ++++----
 security/apparmor/policy.c        | 11 ++++---
 security/apparmor/policy_ns.c     |  8 ++---
 security/apparmor/policy_unpack.c |  2 +-
 security/apparmor/resource.c      |  4 +--
 11 files changed, 91 insertions(+), 71 deletions(-)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

                 reply	other threads:[~2017-11-21 17:08 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=2d41559d-4a1d-c3fb-252e-54a165e7466c@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

all inboxes | Powered by JetHome®