All of lore.kernel.org
 help / color / mirror / Atom feed
From: trix@redhat.com
To: paul@paul-moore.com, stephen.smalley.work@gmail.com,
	eparis@parisplace.org, omosnace@redhat.com, jeffv@google.com,
	rgb@redhat.com
Cc: selinux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tom Rix <trix@redhat.com>
Subject: [PATCH v2 0/1] selinux: fix double free
Date: Wed, 10 Jun 2020 14:57:12 -0700	[thread overview]
Message-ID: <20200610215713.5319-1-trix@redhat.com> (raw)

From: Tom Rix <trix@redhat.com>

repo: linux-next
tag: next-20200610

Running clang scan-view over linux-next uncovers many problem only a
few are memory related, this one looked like the most serious.

Changes from v1

Fix call to kfree
-		kfree(names);
+		kfree(*names);


Tom Rix (1):
  selinux: fix double free

 security/selinux/ss/services.c | 4 ++++
 1 file changed, 4 insertions(+)

-- 
2.18.1


             reply	other threads:[~2020-06-10 21:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 21:57 trix [this message]
2020-06-10 21:57 ` [PATCH v2 1/1] selinux: fix double free trix
2020-06-10 22:06   ` Stephen Smalley
2020-06-11  2:13   ` Paul Moore

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=20200610215713.5319-1-trix@redhat.com \
    --to=trix@redhat.com \
    --cc=eparis@parisplace.org \
    --cc=jeffv@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=rgb@redhat.com \
    --cc=selinux@vger.kernel.org \
    --cc=stephen.smalley.work@gmail.com \
    /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.