Hi Greg, Am 02.02.2012 16:04, schrieb Eric Dumazet:
Hmm, thats a problem, we need a stable 3.0 kernel for sure.Should distros handle this tricky problem themselves ? I tried to find a solution, but we had so many changes in this part of the code that its really hard. I see 3 ways : 1) Warn the world 3.0 is unfixable and should be avoided. Ask stable team to instead support 3.1 or 3.2 2) Disable redirects on 3.0 3) Maybe try to revert f39925dbde77 (ipv4: Cache learned redirect information in inetpeer.) Unfortunately this was introduced in 2.6.39, and it seems trying to revert it on 3.0 tree is not trivial.
as the stable maintainer. What's your opinion? Stefan -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
