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.8 (#1)
Date: Sun, 21 Jun 2020 16:54:16 -0400	[thread overview]
Message-ID: <CAHC9VhQbP754KV8RsaBgnxmuy8gWeL-YccRqQOc8R7DrvtZBvA@mail.gmail.com> (raw)

Hi Linus,

Three small patches to fix problems in the SELinux code, all found via
clang.  Two patches fix potential double-free conditions and one fixes
an undefined return value.  All are pretty easy to understand and the
commit descriptions are reasonably good so I don't think there is a
need to go into more detail here.  Please merge these for v5.8-rcX.

Thanks,
-Paul

--
The following changes since commit fe5a90b8c14914397a3bb0c214d142103c1ba3bf:

 selinux: netlabel: Remove unused inline function
   (2020-05-12 20:16:33 -0400)

are available in the Git repository at:

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

for you to fetch changes up to 8231b0b9c322c894594fb42eb0eb9f93544a6acc:

 selinux: fix undefined return of cond_evaluate_expr
   (2020-06-17 17:36:40 -0400)

----------------------------------------------------------------
selinux/stable-5.8 PR 20200621

----------------------------------------------------------------
Tom Rix (3):
     selinux: fix double free
     selinux: fix a double free in cond_read_node()/cond_read_list()
     selinux: fix undefined return of cond_evaluate_expr

security/selinux/ss/conditional.c | 21 ++++++++-------------
security/selinux/ss/services.c    |  4 ++++
2 files changed, 12 insertions(+), 13 deletions(-)

-- 
paul moore
www.paul-moore.com

             reply	other threads:[~2020-06-21 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21 20:54 Paul Moore [this message]
2020-06-21 22:45 ` [GIT PULL] SELinux fixes for v5.8 (#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=CAHC9VhQbP754KV8RsaBgnxmuy8gWeL-YccRqQOc8R7DrvtZBvA@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.