diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2018-02-23 14:01:52 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-02-23 15:47:20 -0500 |
| commit | 1b71af6053af1bd2f849e9fda4f71c1e3f145dcf (patch) | |
| tree | e639fa9311e511e388b3ccf0efa6cc36abb2bb69 /security | |
| parent | cc30c93fa020e13c91f5076e20062df33f944cdc (diff) | |
| download | linux-stable-1b71af6053af1bd2f849e9fda4f71c1e3f145dcf.tar.gz linux-stable-1b71af6053af1bd2f849e9fda4f71c1e3f145dcf.tar.bz2 linux-stable-1b71af6053af1bd2f849e9fda4f71c1e3f145dcf.zip | |
net: fib_rules: Add new attribute to set protocol
For ages iproute2 has used `struct rtmsg` as the ancillary header for
FIB rules and in the process set the protocol value to RTPROT_BOOT.
Until ca56209a66 ("net: Allow a rule to track originating protocol")
the kernel rules code ignored the protocol value sent from userspace
and always returned 0 in notifications. To avoid incompatibility with
existing iproute2, send the protocol as a new attribute.
Fixes: cac56209a66 ("net: Allow a rule to track originating protocol")
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions