From: Xin Long <lucien.xin@gmail•com>
To: network dev <netdev@vger•kernel.org>
Cc: davem@davemloft•net, David Ahern <dsahern@gmail•com>,
Davide Caratti <dcaratti@redhat•com>,
idosch@idosch•org
Subject: [PATCHv4 net-next 0/2] route: add support and selftests for directed broadcast forwarding
Date: Fri, 27 Jul 2018 16:37:27 +0800 [thread overview]
Message-ID: <cover.1532680283.git.lucien.xin@gmail.com> (raw)
Patch 1/2 is the feature and 2/2 is the selftest. Check the changelog
on each of them to know the details.
v1->v2:
- fix a typo in changelog.
- fix an uapi break that Davide noticed.
- flush route cache when bc_forwarding is changed.
- add the selftest for this patch as Ido's suggestion.
v2->v3:
- fix an incorrect 'if check' in devinet_conf_proc as David Ahern
noticed.
- extend the selftest after one David Ahern fix for vrf.
v3->v4:
- improve the output log in the selftest as David Ahern suggested.
Xin Long (2):
route: add support for directed broadcast forwarding
selftests: add a selftest for directed broadcast forwarding
include/linux/inetdevice.h | 1 +
include/uapi/linux/ip.h | 1 +
include/uapi/linux/netconf.h | 1 +
net/ipv4/devinet.c | 11 +
net/ipv4/route.c | 6 +-
.../selftests/net/forwarding/router_broadcast.sh | 233 +++++++++++++++++++++
6 files changed, 252 insertions(+), 1 deletion(-)
create mode 100755 tools/testing/selftests/net/forwarding/router_broadcast.sh
--
2.1.0
next reply other threads:[~2018-07-27 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 8:37 Xin Long [this message]
2018-07-27 8:37 ` [PATCHv4 net-next 1/2] route: add support for directed broadcast forwarding Xin Long
2018-07-27 8:37 ` [PATCHv4 net-next 2/2] selftests: add a selftest " Xin Long
2018-07-29 19:37 ` [PATCHv4 net-next 0/2] route: add support and selftests " 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=cover.1532680283.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dcaratti@redhat$(echo .)com \
--cc=dsahern@gmail$(echo .)com \
--cc=idosch@idosch$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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