Thanks Eric, Thanks Alex, I think things are as clear as they need to be. I'll add the above Fixes tag and get things queued up. -- To unsubscribe from this list: send the line "unsubscribe lvs-devel
early demux was added in 3.6 Fixes: 41063e9dd119 ("ipv4: Early TCP socket demux.") -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxx
Well this was certainly a problem in 3.10 (we had our own hacky solution at the time) and every kernel since then would have also had this problem. I'm pretty sure this isn't a problem in 3.4 or befo
Thanks. The reason that I am asking about this is to ease getting this fix, or a derivative of it, into the appropriate stable trees. Is there any possibility you could investigate which stable trees
I suppose it'd be appropriate to say Fixes: 41063e9dd119 ("ipv4: Early TCP socket demux.") As that is what introduces tcp early_demux, but that's just a guess as I haven't bisected it (not even sure
Is it possible to get a 'Fixes:' tag? -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.
Yeah this is definitely a crash-fix and it's existed since at least 3.10. -- Alex Gartrell <agartrell@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a
Hello, Thanks for fixing this problem! Acked-by: Julian Anastasov <ja@xxxxxx> May be the patch fixes crashes? If yes, Simon should apply it for ipvs/net tree, otherwise after the merge window... Rega
It is possible that we bind against a local socket in early_demux when we are actually going to want to forward it. In this case, the socket serves no purpose and only serves to confuse things (parti