Sure, if you count in all whitespace/indentation/code moving changes to
that as well... :-)
I might help if would add netdev on cc list in case you really want to
reac net developers, otherwise they might just end up "ignoring it"... ;-)
Those touching fin/close are mostly whitespace/move things, so I doubt
that you find these useful but in case you insist, here's the list:
056834d9f6f6eaf4cc7268569e53acab957aac27 [TCP]: cleanup tcp_{in,out}put.c style
058dc3342b71ffb3531c4f9df7c35f943f392b8d [TCP]: reduce tcp_output's indentation levels a bit
490d5046930276aae50dd16942649bfc626056f7 [TCP]: Uninline tcp_set_state
In addition, there's this one (...though I have read it number of times
through and still cannot catch something that would cause the wrongness
you're seeing):
e870a8efcddaaa3da7e180b6ae21239fb96aa2bb [TCP]: Perform setting of common
control fields in one place
There's very little really on interesting side I can think of, mostly
thinks are congestion control related changes... ...maybe either one of
these could cause something unpleasant in some corner case:
bd515c3e48ececd774eb3128e81b669dbbd32637 [TCP]: Fix TSO deferring
0e3a4803aa06cd7bc2cfc1d04289df4f6027640a [TCP]: Force TSO splits to MSS boundaries
...e.g., if the latter causes a return with zero limit under some
conditions, tso_fragment might generate, well, interesting packets and
never finish if the condition persists but.
--
i.
--
