From: Andrew Morton <akpm@digeo.com>
To: green@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [2.5] memleak in load_elf_binary?
Date: Fri, 7 Mar 2003 03:36:09 -0800 [thread overview]
Message-ID: <20030307033609.2e7fd993.akpm@digeo.com> (raw)
In-Reply-To: <20030307032532.17d37207.akpm@digeo.com>
Andrew Morton <akpm@digeo.com> wrote:
>
> This needs a little thought, as we've already set the new personality and the
> old executable has been rubbed out.
Actually it looks to be fairly simple to fix. Less simple to test...
next prev parent reply other threads:[~2003-03-07 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 11:12 [2.5] memleak in load_elf_binary? Oleg Drokin
2003-03-07 11:25 ` Andrew Morton
2003-03-07 11:36 ` Oleg Drokin
2003-03-07 11:51 ` Andrew Morton
2003-03-07 11:36 ` Andrew Morton [this message]
2003-03-07 20:46 ` Oleg Drokin
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=20030307033609.2e7fd993.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=green@namesys.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