From: David Ashley <dash@xdr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Possible 2.4.18 ipv4 memory leak? [SOLVED!]
Date: Mon, 16 Aug 2004 15:18:15 -0700 [thread overview]
Message-ID: <200408162218.i7GMIF9I024784@xdr.com> (raw)
Tim Schmielau wrote:
>There seem to be quite a few fixes for memory leaks since 2.4.18,
>some network/ethernet related:
>http://linux.bkbits.net:8080/linux-2.4/search/?expr=leak&search=ChangeSet+comments
I followed that link and the second and third lines seemed *very* interesting.
I looked at that patch:
http://linux.bkbits.net:8080/linux-2.4/patch@1.1447.1.19
and back ported it to our 2.4.18 tree (very easy) and that fixed the
problem.
The file was in arch/ppc/8260_io/fcc_enet.c, however the 8260_io directory
became cpm2_io in later versions.
Thanks very much, Tim!
-Dave
reply other threads:[~2004-08-16 22:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200408162218.i7GMIF9I024784@xdr.com \
--to=dash@xdr.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