From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, xiaolong.ye@intel.com
Subject: Re: [PATCH net-next v2] net: ipv6: ignore null_entry on route dumps
Date: Thu, 26 Jan 2017 18:40:05 -0500 (EST) [thread overview]
Message-ID: <20170126.184005.1132641383010709167.davem@davemloft.net> (raw)
In-Reply-To: <1485467648-27922-1-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Thu, 26 Jan 2017 13:54:08 -0800
> Dave: per last email you suggested putting this in fib6_dump_node, but
> fib6_dump_node does not have knowledge of the network namespace
> because of the way the fib_walker works. I could put
> struct rt6_rtnl_dump_arg *arg = (struct rt6_rtnl_dump_arg *) w->args;
> into fib6_dump_node to get the net pointer from it but did not
> want to duplicate the typecast.
Ok, if you can't see the network namespace in fib6_dump_node() you
can't do the test there.
I'll apply this, thanks.
prev parent reply other threads:[~2017-01-26 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 21:54 [PATCH net-next v2] net: ipv6: ignore null_entry on route dumps David Ahern
2017-01-26 23:40 ` 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=20170126.184005.1132641383010709167.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=xiaolong.ye@intel.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