David Miller wrote:
quoted text
> From: Mark Lord <lkml@rtr.ca>
> Date: Wed, 09 Apr 2008 15:05:47 -0400
> 
>> But it would be far more useful for whoever has been working on the
>> stack to suggest some possible/likely commits to look at instead.
> 
> Personally all I see is that one side closes the socket before all
> data packets received have been read into the application, resulting
> in a (correct) reset going out.
> 
> I can't think of any change we've made over the course of this
> release that would change behvaior in that area.
> 
> So you will likely need to bisect.
..

Or I can ignore it, like the net developers, since I have a workaround.
And then we'll see what other apps are broken upon 2.6.25 final release.

Really, folks.  Bug reports are intended to *help* the developers,
not something to be thrown back in their faces.

There do seem to have been a *lot* of changes around the tcp closing/close
code (as I see from diff'ing 2.6.24 against latest -git).

*Somebody* is responsible for those changes.
That particular *somebody* ought to volunteer some help here,
reducing the mountain of commits to a big handful or two.

Cheers
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/