From: David Miller <davem@davemloft.net>
To: dsa@cumulusnetworks.com
Cc: netdev@vger.kernel.org, netdev@linux-dude.de, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] net: ipv6: Add RT6_LOOKUP_F_IFACE flag if oif is set
Date: Tue, 29 Sep 2015 15:01:27 -0700 (PDT) [thread overview]
Message-ID: <20150929.150127.1467318386564675351.davem@davemloft.net> (raw)
In-Reply-To: <1443460333-23302-1-git-send-email-dsa@cumulusnetworks.com>
From: David Ahern <dsa@cumulusnetworks.com>
Date: Mon, 28 Sep 2015 10:12:13 -0700
> Wolfgang reported that IPv6 stack is ignoring oif in output route lookups:
...
> The stack does consider the oif but a mismatch in rt6_device_match is not
> considered fatal because RT6_LOOKUP_F_IFACE is not set in the flags.
>
> Cc: Wolfgang Nothdurft <netdev@linux-dude.de>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
Applied, thank you.
prev parent reply other threads:[~2015-09-29 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 17:12 [PATCH] net: ipv6: Add RT6_LOOKUP_F_IFACE flag if oif is set David Ahern
2015-09-29 22:01 ` 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=20150929.150127.1467318386564675351.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=netdev@linux-dude.de \
--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).