From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cong Wang Subject: Re: [PATCH net] ipv6: no need to return rt->dst.error if it is not null entry. Date: Fri, 21 Jul 2017 11:42:46 -0700 Message-ID: References: <1500562286-14312-1-git-send-email-liuhangbin@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: network dev , Roopa Prabhu To: Hangbin Liu Return-path: Received: from mail-wm0-f50.google.com ([74.125.82.50]:34563 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751504AbdGUSnH (ORCPT ); Fri, 21 Jul 2017 14:43:07 -0400 Received: by mail-wm0-f50.google.com with SMTP id l81so5444662wmg.1 for ; Fri, 21 Jul 2017 11:43:07 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: On Thu, Jul 20, 2017 at 8:23 AM, Hangbin Liu wrote: > 2017-07-20 23:06 GMT+08:00 Hangbin Liu : >>> +++ b/net/ipv6/route.c >>> @@ -3637,12 +3637,6 @@ static int inet6_rtm_getroute(struct sk_buff *in_skb, struct nlmsghdr *nlh, >>> dst = ip6_route_lookup(net, &fl6, 0); >>> >>> rt = container_of(dst, struct rt6_info, dst); >>> - if (rt->dst.error) { >>> - err = rt->dst.error; >>> - ip6_rt_put(rt); >>> - goto errout; >>> - } >> >> hmm... or instead of remove this check, should we check all the entry? Like >> if ((rt->dst.error && rt != net->ipv6.ip6_null_entry && rt != > ^^ mistake here >> net->ipv6.ip6_blk_hole_entry) || >> rt == net->ipv6.ip6_null_entry ) > > Sorry, there should be no need to check ip6_null_entry since the > error is already > -ENETUNREACH. So how about Hmm? All of these 3 entries have error set, right?? So we should only check dst.error...