From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Andrew Morton" <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix memory leak in mm/slab.c::alloc_kmemlist()
Date: Mon, 13 Mar 2006 22:59:46 +0100 [thread overview]
Message-ID: <9a8748490603131359y2f7e3a57p646b8130f23ef59c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603131344480.13027@schroedinger.engr.sgi.com>
On 3/13/06, Christoph Lameter <clameter@sgi.com> wrote:
> On Mon, 13 Mar 2006, Jesper Juhl wrote:
>
> > Ok, I've been playing around with a few ways to resolve this, but I'm
> > a bit pressed for time and won't have properly tested patches ready
> > tonight. I will however keep at this, so you'll see patches
> > releatively shortly, just give me another day or two and I'll have
> > this fixed in a nice way (nice little task to work at :) ...
>
> Maybe extract a alloc_kmemlist_node and free_kmemlist_node from
> alloc_kmemlist()? It gets a bit complicated if all of this is handled within
> alloc_kmemlist and having these separate may simplify recovery on out of
> memory.
>
Nice Idea. So far I've been trying to handle it all inside the
function, but maybe sepperating stuff out might simplify it..
anyway, i'll keep working on this and will submit patches in a day or two...
It really is a nice little problem to work on and I'll find a solution
for it (well, I already have at least one, but it's ugly as hell, want
to find a better one) - gimme a few days.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2006-03-13 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 13:28 Jesper Juhl
2006-03-12 22:41 ` Andrew Morton
2006-03-13 7:34 ` Jesper Juhl
2006-03-13 21:33 ` Jesper Juhl
2006-03-13 21:46 ` Christoph Lameter
2006-03-13 21:59 ` Jesper Juhl [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=9a8748490603131359y2f7e3a57p646b8130f23ef59c@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®