From: Ben Greear <greearb@candelatech.com>
To: Ben Greear <greearb@candelatech.com>
Cc: netdev@vger.kernel.org
Subject: Re: [ipmr] ipmr: Don't leak memory if fib lookup fails.
Date: Thu, 15 Jul 2010 17:04:58 -0700 [thread overview]
Message-ID: <4C3FA22A.7090706@candelatech.com> (raw)
In-Reply-To: <1279236153-23699-1-git-send-email-greearb@candelatech.com>
On 07/15/2010 04:22 PM, Ben Greear wrote:
> This was detected using two mcast router tables. The
> pimreg for the second interface did not have a specific
> mrule, so packets received by it were handled by the
> default table, which had nothing configured.
I just realized this should be applied against 2.6.35-pre, not 2.6.34.
Thanks,
Ben
> This caused the ipmr_fib_lookup to fail, causing
> the memory leak.
>
> Signed-off-by: Ben Greear<greearb@candelatech.com>
> ---
> :100644 100644 ed2f911... f112ad8... M net/ipv4/ipmr.c
> net/ipv4/ipmr.c | 8 ++++++--
> 1 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/net/ipv4/ipmr.c b/net/ipv4/ipmr.c
> index ed2f911..f112ad8 100644
> --- a/net/ipv4/ipmr.c
> +++ b/net/ipv4/ipmr.c
> @@ -442,8 +442,10 @@ static netdev_tx_t reg_vif_xmit(struct sk_buff *skb, struct net_device *dev)
> int err;
>
> err = ipmr_fib_lookup(net,&fl,&mrt);
> - if (err< 0)
> + if (err< 0) {
> + kfree_skb(skb);
> return err;
> + }
>
> read_lock(&mrt_lock);
> dev->stats.tx_bytes += skb->len;
> @@ -1729,8 +1731,10 @@ int ip_mr_input(struct sk_buff *skb)
> goto dont_forward;
>
> err = ipmr_fib_lookup(net,&skb_rtable(skb)->fl,&mrt);
> - if (err< 0)
> + if (err< 0) {
> + kfree_skb(skb);
> return err;
> + }
>
> if (!local) {
> if (IPCB(skb)->opt.router_alert) {
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2010-07-16 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 23:22 [ipmr] ipmr: Don't leak memory if fib lookup fails Ben Greear
2010-07-16 0:04 ` Ben Greear [this message]
2010-07-16 5:39 ` David Miller
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=4C3FA22A.7090706@candelatech.com \
--to=greearb@candelatech.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).