Linux Security Modules development
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [GIT PULL] Security subsystem: Smack updates for v5.2
Date: Fri, 10 May 2019 03:28:49 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.1905100325330.25349@namei.org> (raw)

From Casey: "There's one bug fix for IPv6 handling and two memory use 
improvements."

Plus a couple of further bugfixes.

The following changes since commit fe9fd2ef383c2f5883fcd3f7adce0de9ce2556ff:

  Revert "security: inode: fix a missing check for securityfs_create_file" (2019-04-10 14:59:20 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-smack

for you to fetch changes up to 8d31a5c35ed179825a2145881ad7cd8f9907d94b:

  Merge branch 'smack-for-5.2-b' of https://github.com/cschaufler/next-smack into next-smack (2019-05-06 20:24:51 -0700)

----------------------------------------------------------------
Casey Schaufler (3):
      Smack: Create smack_rule cache to optimize memory usage
      Smack: Fix IPv6 handling of 0 secmark
      Smack: Fix kbuild reported build error

James Morris (3):
      Merge branch 'smack-for-5.2' of https://github.com/cschaufler/next-smack into next-smack
      Merge branch 'smack-for-5.2-b' of https://github.com/cschaufler/next-smack into next-smack
      Merge branch 'smack-for-5.2-b' of https://github.com/cschaufler/next-smack into next-smack

Tetsuo Handa (1):
      smack: Check address length before reading address family

Vishal Goel (1):
      smack: removal of global rule list

 security/smack/smack.h     |  1 +
 security/smack/smack_lsm.c | 34 +++++++++++++++++++++++-----
 security/smack/smackfs.c   | 55 ++++++++++++++--------------------------------
 3 files changed, 45 insertions(+), 45 deletions(-)

             reply	other threads:[~2019-05-09 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 17:28 James Morris [this message]
2019-05-09 20:02 ` [GIT PULL] Security subsystem: Smack updates for v5.2 Linus Torvalds
2019-05-10 10:50   ` Tetsuo Handa
2019-05-10 16:54     ` Linus Torvalds
2019-05-09 20: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=alpine.LRH.2.21.1905100325330.25349@namei.org \
    --to=jmorris@namei.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