Mark frame diverter for future removal.
Subsystems (3)
PATCH 1/1 Mark frame diverter for future removal.
The code for frame diverter is unmaintained and has bitrotted. The number of users is very small and the code has lots of problems. If anyone is using it, they maybe exposing themselves to bad packet attacks.
Signed-off-by Stephen Hemminger <[email protected]>
---
Documentation/feature-removal-schedule.txt | 13 +++++++++++++ net/Kconfig | 2 +- 2 files changed, 14 insertions(+), 1 deletions(-)
3e7063a07247fa424ba225f09c6d9df1a39ac7ba
Documentation/feature-removal-schedule.txt +13 -0
@@ -274,3 +274,16 @@ Why: The deferred output hooks are a lay Who: Patrick McHardy <[email protected]> --------------------------- + +What: frame diverter +When: November 2006 +Why: The frame diverter is included in most distribution kernels, but is + broken. It does not correctly handle many things: + - IPV6 + - non-linear skb's + - network device RCU on removal + - input frames not correctly checked for protocol errors + It also adds allocation overhead even if not enabled. + It is not clear if anyone is still using it. +Who: Stephen Hemminger <[email protected]> +
net/Kconfig +1 -1
@@ -177,7 +177,7 @@ source "net/lapb/Kconfig" config NET_DIVERT bool "Frame Diverter (EXPERIMENTAL)" - depends on EXPERIMENTAL + depends on EXPERIMENTAL && BROKEN ---help--- The Frame Diverter allows you to divert packets from the network, that are not aimed at the interface receiving it (in
Signature · 1 line
1.1.3
Quoted 3 lines · [email protected] said:
The code for frame diverter is unmaintained and has bitrotted. The number of users is very small and the code has lots of problems. If anyone is using it, they maybe exposing themselves to bad packet attacks.
I seem to recall looking at frame diverter and thinking that everything it does can be done with ebtables. All the more reason to remove it.
Jason