summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid S. Miller <davem@sunset.davemloft.net>2007-04-27 01:04:23 -0700
committerDavid S. Miller <davem@sunset.davemloft.net>2007-04-27 01:04:23 -0700
commit49e9f70f8e7a4df00a5185e7f5c91e3c583847db (patch)
treeabd4c6b2406e421530077ec0da884260327fb6f4
parentf16bfc1c0958ff340a02779ab139b03fb5ba6e82 (diff)
downloadkernel-crypto-49e9f70f8e7a4df00a5185e7f5c91e3c583847db.tar.gz
kernel-crypto-49e9f70f8e7a4df00a5185e7f5c91e3c583847db.tar.xz
kernel-crypto-49e9f70f8e7a4df00a5185e7f5c91e3c583847db.zip
[IPV4]: Add multipath cached to feature-removal-schedule.txt
Signed-off-by: David S. Miller <davem@davemloft.net>
-rw-r--r--Documentation/feature-removal-schedule.txt19
1 files changed, 19 insertions, 0 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 976c8a1bd7c..6da663607f7 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -292,3 +292,22 @@ Why: the i8xx_tco watchdog driver has been replaced by the iTCO_wdt
Who: Wim Van Sebroeck <wim@iguana.be>
---------------------------
+
+What: Multipath cached routing support in ipv4
+When: in 2.6.23
+Why: Code was merged, then submitter immediately disappeared leaving
+ us with no maintainer and lots of bugs. The code should not have
+ been merged in the first place, and many aspects of it's
+ implementation are blocking more critical core networking
+ development. It's marked EXPERIMENTAL and no distribution
+ enables it because it cause obscure crashes due to unfixable bugs
+ (interfaces don't return errors so memory allocation can't be
+ handled, calling contexts of these interfaces make handling
+ errors impossible too because they get called after we've
+ totally commited to creating a route object, for example).
+ This problem has existed for years and no forward progress
+ has ever been made, and nobody steps up to try and salvage
+ this code, so we're going to finally just get rid of it.
+Who: David S. Miller <davem@davemloft.net>
+
+---------------------------