From: Yang Hongyang <yanghy@cn.fujitsu.com>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: [RFC][PATCH 3/3]ipv6:fix the outgoing interface selection order in udpv6_sendmsg()
Date: Tue, 09 Dec 2008 15:12:59 +0800 [thread overview]
Message-ID: <493E1A7B.9070208@cn.fujitsu.com> (raw)
1.When no interface is specified in an IPV6_PKTINFO ancillary data
item, the interface specified in an IPV6_PKTINFO sticky optionis
is used.
RFC3542:
6.7. Summary of Outgoing Interface Selection
This document and [RFC-3493] specify various methods that affect the
selection of the packet's outgoing interface. This subsection
summarizes the ordering among those in order to ensure deterministic
behavior.
For a given outgoing packet on a given socket, the outgoing interface
is determined in the following order:
1. if an interface is specified in an IPV6_PKTINFO ancillary data
item, the interface is used.
2. otherwise, if an interface is specified in an IPV6_PKTINFO sticky
option, the interface is used.
Signed-off-by: Yang Hongyang<yanghy@cn.fujitsu.com>
---
net/ipv6/udp.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/net/ipv6/udp.c b/net/ipv6/udp.c
index 8b48512..addd856 100644
--- a/net/ipv6/udp.c
+++ b/net/ipv6/udp.c
@@ -761,6 +761,9 @@ do_udp_sendmsg:
}
if (!fl.oif)
+ fl.oif = np->sticky_pktinfo.ipi6_ifindex;
+
+ if (!fl.oif)
fl.oif = sk->sk_bound_dev_if;
if (msg->msg_controllen) {
--
1.6.0.1
next reply other threads:[~2008-12-09 7:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 7:12 Yang Hongyang [this message]
2008-12-09 7:32 ` [RFC][PATCH 3/3]ipv6:fix the outgoing interface selection order in udpv6_sendmsg() Rémi Denis-Courmont
2008-12-10 0:42 ` Yang Hongyang
2008-12-10 6:16 ` David Miller
2008-12-10 6:33 ` Yang Hongyang
2008-12-10 6:38 ` Yang Hongyang
2008-12-10 9:15 ` David Miller
2008-12-10 9:41 ` Yang Hongyang
2008-12-16 10:09 ` David Miller
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=493E1A7B.9070208@cn.fujitsu.com \
--to=yanghy@cn.fujitsu.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).