From: "David S. Miller" <davem@redhat.com>
To: krkumar@us.ibm.com
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] memory leak in ndisc_router_discovery
Date: Fri, 20 Dec 2002 23:08:36 -0800 (PST) [thread overview]
Message-ID: <20021220.230836.40590865.davem@redhat.com> (raw)
In-Reply-To: <200212121905.gBCJ5hn18058@eng2.beaverton.ibm.com>
From: Krishna Kumar <krkumar@us.ibm.com>
Date: Thu, 12 Dec 2002 11:05:43 -0800 (PST)
I had sent this earlier, there is a bug in router advertisement handling code,
where the reference (and memory) to an inet6_dev pointer can get leaked (this
leak can happen atmost once for each interface on a system which receives
invalid RA's). Below is the patch against 2.5.51 to fix it.
Applied, thanks.
prev parent reply other threads:[~2002-12-21 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 19:05 [PATCH RESEND] memory leak in ndisc_router_discovery Krishna Kumar
2002-12-16 6:35 ` YOSHIFUJI Hideaki / 吉藤英明
2002-12-21 7:08 ` David S. Miller [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=20021220.230836.40590865.davem@redhat.com \
--to=davem@redhat.com \
--cc=krkumar@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).