netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, xiaolong.ye@intel.com
Subject: Re: [PATCH net-next] net: ipv6: ignore null_entry on route dumps
Date: Sun, 22 Jan 2017 23:58:29 -0500 (EST)	[thread overview]
Message-ID: <20170122.235829.1911961579892347071.davem@davemloft.net> (raw)
In-Reply-To: <1485147377-11922-1-git-send-email-dsa@cumulusnetworks.com>


David, please slow down.

How is the NULL entry getting selected to be dumped and passed
down here in the first place?

The problem seems to be higher up in the chain here, don't
just special case check for this in rt6_dump_route().

Thanks.

  reply	other threads:[~2017-01-23  4:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23  4:56 [PATCH net-next] net: ipv6: ignore null_entry on route dumps David Ahern
2017-01-23  4:58 ` David Miller [this message]
2017-01-23 16:51   ` David Ahern
2017-01-25  1:35     ` David Ahern
2017-01-25  1:39       ` David Miller
2017-01-25  4:07         ` David Ahern

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=20170122.235829.1911961579892347071.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;
as well as URLs for NNTP newsgroup(s).