linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] security: Smack updates for v4.20
Date: Thu, 25 Oct 2018 20:37:41 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.21.1810252035220.30470@namei.org> (raw)

Please pull.

From Casey: "Here are three patches for Smack for 4.20. Two clean up 
warnings and one is a rarely encountered ptrace capability check."

---

The following changes since commit 0d42d73a37ff91028785e42a6bf12fc020a277c1:

  seccomp: remove unnecessary unlikely() (2018-09-06 13:29:59 -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 f0f9756b7260f4e78a2e4e412a55167178721ca2:

  Merge branch 'smack-for-4.20' of https://github.com/cschaufler/next-smack into next-smack (2018-09-25 11:15:12 -0700)

----------------------------------------------------------------
Casey Schaufler (1):
      Smack: ptrace capability use fixes

Gustavo A. R. Silva (1):
      Smack: Mark expected switch fall-through

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

YueHaibing (1):
      Smack: remove set but not used variable 'root_inode'

 security/smack/smack_lsm.c | 15 +++++++++++----
 security/smack/smackfs.c   |  3 ---
 2 files changed, 11 insertions(+), 7 deletions(-)

             reply	other threads:[~2018-10-25  9:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25  9:37 James Morris [this message]
2018-10-25 20:30 ` Linus Torvalds

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.1810252035220.30470@namei.org \
    --to=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] security: Smack updates for v4.20' \
    /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

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).