Re: dccp bugs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



| > If possible, can you please try the test tree patches and see if the
| > problem persists. I am doing a lot of testing and have not observed any
| > similar errors in the test tree -- the closest being the server-hand on
| > retransmitting CloseReq, which may account for the earlier confusion.
| >
| Yes, it works ok now. I was already using the test tree before but the wrong 
| branch.
Thanks very much for testing. I have a suspicion that the fix is in one
of the following patches:

 [CCID]: Refine the wait-for-ccid mechanism        
 [DCCP]: Empty the write queue when disconnecting 

Both flush the write queue on exit. The first one limits the amount of
time that close() will allow to drain the write queue, the second patch
flushes the write queue when the connection is aborted.


The University of Aberdeen is a charity registered in Scotland, No SC013683.

--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [IETF DCCP]     [Linux Networking]     [Git]     [Security]     [Linux Assembly]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux