linux-security-module.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,
	David Howells <dhowells@redhat.com>
Subject: [GIT PULL] KEYS: fixes for v5.1
Date: Sat, 16 Feb 2019 09:16:00 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LRH.2.21.1902160914180.4453@namei.org> (raw)

Hi Linus,

Please pull these fixes for the Keys subsystem.

From David Howells:

" (1) Handle quotas better, allowing full quota to be reached.

 (2) Fix the creation of shortcuts in the assoc_array internal
     representation when the index key needs to be an exact multiple of the
     machine word size.

 (3) Fix a dependency loop between the request_key contruction record and
     the request_key authentication key.  The construction record isn't
     really necessary and can be dispensed with.

 (4) Set the timestamp on a new key rather than leaving it as 0.  This
     would ordinarily be fine - provided the system clock is never set to a
     time before 1970."

---

The following changes since commit 5ded5871030eb75017639148da0a58931dfbfc25:

  Merge tag 'scsi-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi (2019-02-15 13:36:43 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git fixes-v5.1-rc6

for you to fetch changes up to 7c1857bdbdf1e4c541e45eab477ee23ed4333ea4:

  keys: Timestamp new keys (2019-02-15 14:12:09 -0800)

----------------------------------------------------------------
David Howells (3):
      assoc_array: Fix shortcut creation
      keys: Fix dependency loop between construction record and auth key
      keys: Timestamp new keys

Eric Biggers (1):
      KEYS: allow reaching the keys quotas exactly

 fs/nfs/nfs4idmap.c                   | 31 +++++++++-------
 include/keys/request_key_auth-type.h | 36 ++++++++++++++++++
 include/linux/key-type.h             | 22 +++--------
 lib/assoc_array.c                    |  8 ++--
 security/keys/internal.h             | 13 +------
 security/keys/key.c                  |  5 ++-
 security/keys/keyctl.c               |  1 +
 security/keys/process_keys.c         |  1 +
 security/keys/request_key.c          | 72 +++++++++++++++---------------------
 security/keys/request_key_auth.c     | 16 ++++----
 10 files changed, 108 insertions(+), 97 deletions(-)
 create mode 100644 include/keys/request_key_auth-type.h

             reply	other threads:[~2019-02-15 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 22:16 James Morris [this message]
2019-02-17  1:46 ` [GIT PULL] KEYS: fixes for v5.1 Linus Torvalds
2019-02-19 19:06   ` James Morris
2019-02-20 17: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.1902160914180.4453@namei.org \
    --to=jmorris@namei.org \
    --cc=dhowells@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).