mirror of https://lore.kernel.org/lkml/
 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: Smack changes for v4.21
Date: Mon, 31 Dec 2018 15:16:25 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.21.1812311515150.1435@namei.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

From Casey:

"I have two Smack patches for 4.21. One Jose's patch adds
missing documentation and Zoran's fleshes out the access checks
on keyrings."

The following changes since commit 1072bd678547f8663cfb81a22fdb50c589e4976e:

  security: fs: make inode explicitly non-modular (2018-12-12 14:58:51 -0800)

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 20bb4cb4fb9fb994d757932abc4404cf0f0f56cc:

  Merge branch 'smack-for-4.21-a' of https://github.com/cschaufler/next-smack into next-smack (2018-12-13 19:30:33 -0800)

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

José Bollo (1):
      Smack: Improve Documentation

Zoran Markovic (1):
      smack: fix access permissions for keyring

 Documentation/admin-guide/LSM/Smack.rst |  4 ++++
 security/smack/smack_lsm.c              | 12 +++++++++---
 2 files changed, 13 insertions(+), 3 deletions(-)

             reply	other threads:[~2018-12-31  4:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31  4:16 James Morris [this message]
2019-01-02 19:10 ` 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.1812311515150.1435@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

all inboxes | Powered by JetHome®