From: David Miller <davem@davemloft.net>
To: dsahern@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v3 net] net/ipv6: Handle onlink flag with multipath routes
Date: Thu, 22 Mar 2018 12:40:38 -0400 (EDT) [thread overview]
Message-ID: <20180322.124038.485987673025634432.davem@davemloft.net> (raw)
In-Reply-To: <20180320170659.31625-1-dsahern@gmail.com>
From: David Ahern <dsahern@gmail.com>
Date: Tue, 20 Mar 2018 10:06:59 -0700
> For multipath routes the ONLINK flag can be specified per nexthop in
> rtnh_flags or globally in rtm_flags. Update ip6_route_multipath_add
> to consider the ONLINK setting coming from rtnh_flags. Each loop over
> nexthops the config for the sibling route is initialized to the global
> config and then per nexthop settings overlayed. The flag is 'or'ed into
> fib6_config to handle the ONLINK flag coming from either rtm_flags or
> rtnh_flags.
>
> Fixes: fc1e64e1092f ("net/ipv6: Add support for onlink flag")
> Signed-off-by: David Ahern <dsahern@gmail.com>
Applied, thanks David.
prev parent reply other threads:[~2018-03-22 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:06 [PATCH v3 net] net/ipv6: Handle onlink flag with multipath routes David Ahern
2018-03-22 16: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=20180322.124038.485987673025634432.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.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