netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: roy.qing.li@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] ipv6: release idev when ip6_neigh_lookup failed in icmp6_dst_alloc
Date: Fri, 13 Jan 2012 10:11:09 -0800 (PST)	[thread overview]
Message-ID: <20120113.101109.1309327184308507695.davem@davemloft.net> (raw)
In-Reply-To: <1326448121.2272.4.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 13 Jan 2012 10:48:41 +0100

> Le vendredi 13 janvier 2012 à 16:33 +0800, roy.qing.li@gmail.com a
> écrit :
>> From: RongQing.Li <roy.qing.li@gmail.com>
>> 
>> release idev when ip6_neigh_lookup failed in icmp6_dst_alloc
>> 
>> Signed-off-by: RongQing.Li <roy.qing.li@gmail.com>
>> ---
>>  net/ipv6/route.c |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>> 
>> diff --git a/net/ipv6/route.c b/net/ipv6/route.c
>> index 07361df..8c2e3ab 100644
>> --- a/net/ipv6/route.c
>> +++ b/net/ipv6/route.c
>> @@ -1091,6 +1091,7 @@ struct dst_entry *icmp6_dst_alloc(struct net_device *dev,
>>  	else {
>>  		neigh = ip6_neigh_lookup(&rt->dst, &fl6->daddr);
>>  		if (IS_ERR(neigh)) {
>> +			in6_dev_put(idev);
>>  			dst_free(&rt->dst);
>>  			return ERR_CAST(neigh);
>>  		}
> 
> Good catch, thanks.
> 
> Bug added in commit b43faac6906 (ipv6: If neigh lookup fails during
> icmp6 dst allocation, propagate error.), 
> 
> Acked-by: Eric Dumazet <eric.dumazet@gmail.com>

Applied, thanks everyone.

      reply	other threads:[~2012-01-13 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13  8:33 [PATCH] ipv6: release idev when ip6_neigh_lookup failed in icmp6_dst_alloc roy.qing.li
2012-01-13  9:48 ` Eric Dumazet
2012-01-13 18:11   ` David 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=20120113.101109.1309327184308507695.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=roy.qing.li@gmail.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).