Comment 7 for bug 567394

Revision history for this message
Stefan Bader (smb) wrote :

When I read back there, it seems the first two mentioned patches alone were not helping. Looking into the 2.6.25.7 range it seems there is a range of 5 patches that could be touching the problem area:

commit 7a0c866aacab51afa7a6cbf6eccf5e1aa5fd64b9
Author: Ilpo Järvinen <email address hidden>

    tcp: Fix inconsistency source (CA_Open only when !tcp_left_out(tp))

commit 99d737e98d81762332242cc82e5604520842911a
Author: Ilpo Järvinen <email address hidden>

    tcp FRTO: work-around inorder receivers

commit 59a16700219922a1b095abd76caa25fd4417470c
Author: Ilpo Järvinen <email address hidden>

    tcp FRTO: SACK variant is errorneously used with NewReno

commit 76ab0a7c88886400dd16870db65106215f3e4aa3
Author: Ilpo Järvinen <email address hidden>

    tcp FRTO: Fix fallback to conventional recovery

commit 47478b42b8e74c2311674eda6700a0ced1509383
Author: Ilpo Järvinen <email address hidden>

    tcp: fix skb vs fack_count out-of-sync condition