From: David Ahern <dsahern@gmail.com>
To: Jeff Barnhill <0xeffeff@gmail.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCH net v5] net/ipv6: Add anycast addresses to a global hashtable
Date: Wed, 31 Oct 2018 20:53:57 -0600 [thread overview]
Message-ID: <3328ed3b-0c7f-e763-bfe7-0cef8ddcbb03@gmail.com> (raw)
In-Reply-To: <CAL6e_pfzPzt=rAxjWKAWHQqdrqejZ5e6vA1YoB3nGyc3_jeJeA@mail.gmail.com>
On 10/31/18 6:02 PM, Jeff Barnhill wrote:
> I'll follow this email with a new patch using ifacaddr6 instead of
> creating a new struct. I ended up using fib6_nh.nh_dev to get the net,
> instead of adding a back pointer to idev. It seems that idev was
> recently removed in lieu of this, so if this is incorrect, please let
> me know. Hopefully, I got the locking correct.
That's correct. Make sure that the anycast code can not be accessed for
reject routes which will not have a device set. Should be ok, but double
check.
prev parent reply other threads:[~2018-11-01 11:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 2:12 [PATCH net] net/ipv6: Add anycast addresses to a global hashtable Jeff Barnhill
2018-10-23 2:26 ` Eric Dumazet
2018-10-23 18:21 ` Jeff Barnhill
2018-10-24 1:58 ` [PATCH net v2] " Jeff Barnhill
2018-10-24 3:12 ` Eric Dumazet
2018-10-24 5:06 ` Jeff Barnhill
2018-10-26 21:22 ` [PATCH net v3] " Jeff Barnhill
2018-10-26 21:44 ` David Ahern
2018-10-27 18:02 ` [PATCH net v4] " Jeff Barnhill
2018-10-27 23:39 ` David Ahern
2018-10-28 1:27 ` Jeff Barnhill
2018-10-28 1:51 ` [PATCH net v5] " Jeff Barnhill
2018-10-30 3:32 ` David Miller
2018-10-30 11:10 ` Jeff Barnhill
2018-10-30 18:31 ` David Miller
2018-10-30 22:06 ` David Ahern
2018-10-30 23:19 ` David Miller
2018-11-01 0:02 ` Jeff Barnhill
2018-11-01 0:14 ` [PATCH net v6] " Jeff Barnhill
2018-11-01 5:34 ` Stephen Hemminger
2018-11-02 20:23 ` [PATCH net v7] " Jeff Barnhill
2018-11-03 6:55 ` David Miller
2018-11-01 2:53 ` David Ahern [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=3328ed3b-0c7f-e763-bfe7-0cef8ddcbb03@gmail.com \
--to=dsahern@gmail.com \
--cc=0xeffeff@gmail.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).