mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, d.kasatkin@samsung.com,
	casey@schaufler-ca.com, keyrings@linux-nfs.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] KEYS: Make perm request flags available to security modules
Date: Mon, 31 Mar 2014 14:28:25 +0100	[thread overview]
Message-ID: <8321.1396272505@warthog.procyon.org.uk> (raw)


Hi Linus,

Can you pull this pair of patches please?  They move the flags that are used
to request specific permissions to a more public header file so that they can
then be used by Smack (and other security modules).

The flags for requesting permissions on keys are not the same as the flags in
the permissions mask on a key (the latter has four sets that interact).

Note that the flags have to be renamed so that they don't conflict with
input symbols (eg. keyboard key names).

David
---
The following changes since commit c60f7d5a8e7c639de5d9dfe07e1e91d302d506e4:

  Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux (2014-03-13 21:32:16 -0700)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-20140314

for you to fetch changes up to fffea214abf66a8672cfd6697fae65e743e22f11:

  smack: fix key permission verification (2014-03-14 17:44:49 +0000)

----------------------------------------------------------------
(from the branch description for keys-dmitry local branch)

Keyrings stuff for/from Dmitry Kasatkin
Keyrings changes

----------------------------------------------------------------
David Howells (1):
      KEYS: Move the flags representing required permission to linux/key.h

Dmitry Kasatkin (1):
      smack: fix key permission verification

 include/linux/key.h        | 11 +++++++++++
 include/linux/security.h   |  6 +++---
 security/capability.c      |  2 +-
 security/keys/internal.h   | 11 +----------
 security/keys/key.c        |  6 +++---
 security/keys/keyctl.c     | 44 ++++++++++++++++++++++----------------------
 security/keys/keyring.c    |  8 ++++----
 security/keys/permission.c |  4 ++--
 security/keys/persistent.c |  4 ++--
 security/keys/proc.c       |  2 +-
 security/security.c        |  2 +-
 security/selinux/hooks.c   |  2 +-
 security/smack/smack_lsm.c |  9 +++++++--
 13 files changed, 59 insertions(+), 52 deletions(-)

             reply	other threads:[~2014-03-31 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 13:28 David Howells [this message]
2014-03-31 15:32 ` James Morris
2014-03-31 15:54 ` David Howells
2014-03-31 23:30   ` James Morris
2014-04-14  1:39     ` James Morris

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=8321.1396272505@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=casey@schaufler-ca.com \
    --cc=d.kasatkin@samsung.com \
    --cc=keyrings@linux-nfs.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®