From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
Eric Biederman <ebiederm@xmission.com>,
Julian Anastasov <ja@ssi.bg>,
"David S. Miller" <davem@davemloft.net>,
Cong Wang <cwang@twopensource.com>
Subject: [Patch net v2 0/2] ipv4: fix flowi4_iif for input routing
Date: Tue, 15 Apr 2014 16:25:33 -0700 [thread overview]
Message-ID: <1397604335-12752-1-git-send-email-xiyou.wangcong@gmail.com> (raw)
This patchset fixes ->flowi4_iif for input routing and rp filter,
based on suggestion from Julian. See per patch for details.
v1 -> v2:
* merge the first two patches into one
* fix fib_check_nh() too
* add this cover letter
Cc: Eric Biederman <ebiederm@xmission.com>
Cc: Julian Anastasov <ja@ssi.bg>
Cc: David S. Miller <davem@davemloft.net>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
Signed-off-by: Cong Wang <cwang@twopensource.com>
Cong Wang (2):
ipv4,fib: pass LOOPBACK_IFINDEX instead of 0 to flowi4_iif
ipv4,route: pass 0 instead of LOOPBACK_IFINDEX to
fib_validate_source()
include/net/flow.h | 10 +++++++++-
include/net/net_namespace.h | 9 +--------
net/ipv4/fib_frontend.c | 2 +-
net/ipv4/fib_semantics.c | 1 +
net/ipv4/ipmr.c | 2 +-
net/ipv4/netfilter/ipt_rpfilter.c | 5 +----
net/ipv4/route.c | 3 +--
net/ipv6/ip6mr.c | 2 +-
8 files changed, 16 insertions(+), 18 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-04-15 23:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 23:25 Cong Wang [this message]
2014-04-15 23:25 ` [Patch net v2 1/2] ipv4,fib: pass LOOPBACK_IFINDEX instead of 0 to flowi4_iif Cong Wang
2014-04-15 23:25 ` [Patch net v2 2/2] ipv4,route: pass 0 instead of LOOPBACK_IFINDEX to fib_validate_source() Cong Wang
2014-04-16 5:42 ` [Patch net v2 0/2] ipv4: fix flowi4_iif for input routing Julian Anastasov
2014-04-16 19:06 ` 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=1397604335-12752-1-git-send-email-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=cwang@twopensource.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=ja@ssi.bg \
--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).