From: James Morris <jmorris@namei.org>
To: Catherine Zhang <cxzhang@watson.ibm.com>
Cc: linux-kernel@vger.kernel.org, michal.k.k.piotrowski@gmail.com,
catalin.marinas@gmail.com, czhang.us@gmail.com,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: kernel memory leak fix for af_unix datagram getpeersec
Date: Sun, 16 Jul 2006 00:57:34 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607160052570.30274@d.namei> (raw)
In-Reply-To: <20060716045731.GA303@jiayuguan.watson.ibm.com>
On Sun, 16 Jul 2006, Catherine Zhang wrote:
>
> Hi, Catalin and Michal,
>
> Enclosed please find the patch against 2.6.18-rc1 that fixed the kernel
> memory leak problem.
The core kernel code doesn't know anything about secdata, as it is up to
the LSM to determine what it is (in the case of SELinux, a kmalloc'd
buffer).
So, you need a cleanup hook which allows the LSM to free the secdata if
required.
- James
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2006-07-16 4:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 4:57 Catherine Zhang
2006-07-16 4:57 ` James Morris [this message]
2006-07-16 11:16 ` Michal Piotrowski
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=Pine.LNX.4.64.0607160052570.30274@d.namei \
--to=jmorris@namei.org \
--cc=catalin.marinas@gmail.com \
--cc=cxzhang@watson.ibm.com \
--cc=czhang.us@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=sds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®