From: "Paul Moore" <paul.moore@hp.com>
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Subject: [PATCH 0/2] Small memory-leak patchset
Date: Wed, 01 Aug 2007 11:12:57 -0400 [thread overview]
Message-ID: <20070801151257.475951538@hp.com> (raw)
While doing some other work I found some small memory leaks with the way
we are using security_secid_to_secctx() in some of the auditing code paths.
We also had a redundant NULL pointer check in the SELinux function which frees
the leaked memory. This patchset fixes both of these issues.
This patchset is backed against Linus' tree from this morning and has been
lightly tested.
--
paul moore
linux security @ hp
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
WARNING: multiple messages have this Message-ID (diff)
From: "Paul Moore" <paul.moore@hp.com>
To: netdev@vger.kernel.org, selinux@tycho.nsa.gov
Subject: [PATCH 0/2] Small memory-leak patchset
Date: Wed, 01 Aug 2007 11:12:57 -0400 [thread overview]
Message-ID: <20070801151257.475951538@hp.com> (raw)
While doing some other work I found some small memory leaks with the way
we are using security_secid_to_secctx() in some of the auditing code paths.
We also had a redundant NULL pointer check in the SELinux function which frees
the leaked memory. This patchset fixes both of these issues.
This patchset is backed against Linus' tree from this morning and has been
lightly tested.
--
paul moore
linux security @ hp
next reply other threads:[~2007-08-01 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 15:12 Paul Moore [this message]
2007-08-01 15:12 ` [PATCH 0/2] Small memory-leak patchset Paul Moore
2007-08-01 15:12 ` [PATCH 1/2] SELinux: remove redundant pointer checks before calling kfree() Paul Moore
2007-08-01 15:12 ` Paul Moore
2007-08-01 15:12 ` [PATCH 2/2] NET: fix memory leaks from security_secid_to_secctx() Paul Moore
2007-08-01 15:12 ` Paul Moore
2007-08-02 0:05 ` James Morris
2007-08-02 0:05 ` James Morris
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=20070801151257.475951538@hp.com \
--to=paul.moore@hp.com \
--cc=netdev@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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.