diff options
| author | David S. Miller <davem@davemloft.net> | 2016-09-09 16:50:23 -0700 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-09-09 16:50:23 -0700 |
| commit | a349fcc85fc67d6a793104bfa0d5b31220b57752 (patch) | |
| tree | ff62c797d7d70abbcf4d32bdb57bd1f9beda37b0 /net/core/rtnetlink.c | |
| parent | e895cdce683161081e3626c4f5a5c55cb72089f8 (diff) | |
| parent | 73483c1289d148282be3aac3ad30b4aa1f8fac87 (diff) | |
| download | op-kernel-dev-a349fcc85fc67d6a793104bfa0d5b31220b57752.zip op-kernel-dev-a349fcc85fc67d6a793104bfa0d5b31220b57752.tar.gz | |
Merge branch 'newroute-creation-flags'
Guillaume Nault says:
====================
ip: fix creation flags reported in RTM_NEWROUTE events
Netlink messages sent to user-space upon RTM_NEWROUTE events have their
nlmsg_flags field inconsistently set. While the NLM_F_REPLACE and
NLM_F_APPEND bits are correctly handled, NLM_F_CREATE and NLM_F_EXCL
are always 0.
This series sets the NLM_F_CREATE and NLM_F_EXCL bits when applicable,
for IPv4 and IPv6.
Since IPv6 ignores the NLM_F_APPEND flags in requests, this flag isn't
reported in RTM_NEWROUTE IPv6 events. This keeps IPv6 internal
consistency (same flag semantic for user requests and kernel events) at
the cost of bringing different flag interpretation for IPv4 and IPv6.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core/rtnetlink.c')
0 files changed, 0 insertions, 0 deletions
