From: Paul Moore <paul.moore@hp.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Memory leak in security_netlbl_sid_to_secattr(), kernel 2.6.23.12
Date: Fri, 18 Jan 2008 22:35:30 -0500 [thread overview]
Message-ID: <200801182235.31189.paul.moore@hp.com> (raw)
In-Reply-To: <47913417.3090504@redhat.com>
On Friday 18 January 2008 6:19:51 pm Chuck Ebbert wrote:
> We have two reports of this now.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=352281
>
> The user enabled SLUB user tracing and reports that the entries
> created by security_netlbl_sid_to_secattr() were increasing the
> most. Disabling selinux makes the problem go away completely.
Thanks for the report, sorry about the leak. I just posted an RFC patch, CC'd
to you, which I believe should fix the problem. I did a quick compile test
on the SELinux module but I am "on vacation" with family visiting so I am
currently unable to do any real testing until next week.
I've added myself to the bugzilla, but if you are able to do any tests please
let me know if the patch does or does not solve the problem.
Thanks.
--
paul moore
linux security @ hp
prev parent reply other threads:[~2008-01-19 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 23:19 Memory leak in security_netlbl_sid_to_secattr(), kernel 2.6.23.12 Chuck Ebbert
2008-01-19 3:35 ` Paul Moore [this message]
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=200801182235.31189.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=cebbert@redhat.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).