K 10
svn:author
V 2
bz
K 8
svn:date
V 27
2008-09-07T11:38:30.134656Z
K 7
svn:log
V 345
Add a second KASSERT checking for len >= 0 in the tcp output path.

This is different to the first one (as len gets updated between those
two) and would have caught various edge cases (read bugs) at a well
defined place I had been debugging the last months instead of
triggering (random) panics further down the call graph.

MFC after:	2 months

END