From: Ben Greear <greearb@candelatech.com>
To: Michael Rozhavsky <mrozhavsky@mrv.com>
Cc: vlan@scry.wanfear.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8021q memory leak
Date: Thu, 30 Jan 2003 11:15:51 -0800 [thread overview]
Message-ID: <3E3979E7.2080908@candelatech.com> (raw)
In-Reply-To: <20030130182936.GC3348@mike.nbase.co.il>
Michael Rozhavsky wrote:
> Hi,
>
> There is a memory leak in vlan module of 2.4.20
>
> When last vlan of the group is removed the group is unhashed but not
> deleted.
>
> Attached patch fixes this memory leak and completes implementation of
> memory debug output.
I believe some of the memory leaks were fixed in the -pre3 patch.
I'll wander through the code to make sure that the ones you found
were addressed.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2003-01-30 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 18:29 [PATCH] 8021q memory leak Michael Rozhavsky
2003-01-30 19:15 ` Ben Greear [this message]
2003-01-31 8:25 ` David S. Miller
2003-01-31 10:58 ` Michael Rozhavsky
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=3E3979E7.2080908@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrozhavsky@mrv.com \
--cc=vlan@scry.wanfear.com \
/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