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-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Security subsystem fixes for v5.8
Date: Tue, 30 Jun 2020 07:00:03 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LRH.2.21.2006300659080.10756@namei.org> (raw)

Please pull (now using signed tags).

The following changes since commit 48778464bb7d346b47157d21ffde2af6b2d39110:

  Linux 5.8-rc2 (2020-06-21 15:45:29 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git tags/fixes-v5.8-rc3-a

for you to fetch changes up to 23e390cdbe6f85827a43d38f9288dcd3066fa376:

  security: Fix hook iteration and default value for inode_copy_up_xattr (2020-06-23 16:39:23 -0700)

----------------------------------------------------------------
Two simple fixes for v5.8:

1) Fix hook iteration and default value for inode_copy_up_xattr
	from KP Singh <kpsingh@google.com>

2) Fix the key_permission LSM hook function type
	from Sami Tolvanen <samitolvanen@google.com>

----------------------------------------------------------------
KP Singh (1):
      security: Fix hook iteration and default value for inode_copy_up_xattr

Sami Tolvanen (1):
      security: fix the key_permission LSM hook function type

 include/linux/lsm_hook_defs.h |  4 ++--
 security/security.c           | 17 ++++++++++++++++-
 2 files changed, 18 insertions(+), 3 deletions(-)

             reply	other threads:[~2020-06-29 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 21:00 James Morris [this message]
2020-07-01 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.2006300659080.10756@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®