All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: selinux@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] SELinux fixes for v5.10 (#1)
Date: Fri, 13 Nov 2020 18:29:23 -0500	[thread overview]
Message-ID: <CAHC9VhSrJLtasTbE+smvHYMxD3B018TCLx74y9RQ0pk8jDaX4w@mail.gmail.com> (raw)

Hi Linus,

One small SELinux patch for v5.10-rcX to make sure we return an error
code when an allocation fails.  It passes all of our tests, but given
the nature of the patch that isn't surprising.  Please merge during
the v5.10-rcX cycle.

Thanks,
-Paul

--
The following changes since commit 0d50f059c4cdc9e436f6f4db8779ac0795bfdadf:

 selinux: provide a "no sooner than" date for the checkreqprot removal
   (2020-09-29 16:50:57 -0400)

are available in the Git repository at:

 git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git
   tags/selinux-pr-20201113

for you to fetch changes up to c350f8bea271782e2733419bd2ab9bf4ec2051ef:

 selinux: Fix error return code in sel_ib_pkey_sid_slow()
   (2020-11-12 20:16:09-0500)

----------------------------------------------------------------
selinux/stable-5.10 PR 20201113

----------------------------------------------------------------
Chen Zhou (1):
     selinux: Fix error return code in sel_ib_pkey_sid_slow()

security/selinux/ibpkey.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)

-- 
paul moore
www.paul-moore.com

             reply	other threads:[~2020-11-13 23:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 23:29 Paul Moore [this message]
2020-11-14 20:51 ` [GIT PULL] SELinux fixes for v5.10 (#1) 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=CAHC9VhSrJLtasTbE+smvHYMxD3B018TCLx74y9RQ0pk8jDaX4w@mail.gmail.com \
    --to=paul@paul-moore.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=selinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.