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.16 (#2)
Date: Tue, 23 Nov 2021 16:52:30 -0500	[thread overview]
Message-ID: <CAHC9VhS2Hqg2rvS=Fbkpj++HEs5Cxf=4Xcmd7kdgvOykY1Os+A@mail.gmail.com> (raw)

Hi Linus,

A small SELinux fix for v5.16.  As usual the commit description has
more detail, but it's basically a fix to make sure things are handled
correctly when an allocation fails; please merge.

Thanks,
-Paul

--
The following changes since commit 32a370abf12f82c8383e430c21365f5355d8b288:

 net,lsm,selinux: revert the security_sctp_assoc_established() hook
   (2021-11-12 12:07:02 -0500)

are available in the Git repository at:

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

for you to fetch changes up to dc27f3c5d10c58069672215787a96b4fae01818b:

 selinux: fix NULL-pointer dereference when hashtab allocation fails
   (2021-11-19 16:11:39 -0500)

----------------------------------------------------------------
selinux/stable-5.16 PR 20211123

----------------------------------------------------------------
Ondrej Mosnacek (1):
     selinux: fix NULL-pointer dereference when hashtab allocation fails

security/selinux/ss/hashtab.c | 17 ++++++++++++-----
1 file changed, 12 insertions(+), 5 deletions(-)

-- 
paul moore
www.paul-moore.com

             reply	other threads:[~2021-11-23 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 21:52 Paul Moore [this message]
2021-11-23 22:05 ` [GIT PULL] SELinux fixes for v5.16 (#2) 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='CAHC9VhS2Hqg2rvS=Fbkpj++HEs5Cxf=4Xcmd7kdgvOykY1Os+A@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.