On 7/13/07, Gerrit Renker <gerrit@xxxxxxxxxxxxxx> wrote: > [DCCP]: Basic support for passive-close > > This implements necessary state transitions for the two forms of passive-close > > * PASSIVE_1, which is entered when a host receives Close; > * PASSIVE_2, which is entered when a client receives CloseReq. > > The handling is such that these passive connection-termination requests are > enqueued as `fin' packets so that dccp_recvmsg() can later detect them. The > only thing I am not entirely sure about is the wake_async in dccp_rcv_closereq(); > this has been copied from dccp_rcv_close() (but looks ok from the principle). > > The completed state transition diagram is on > http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/closing_states/ > > NB: Regrettably, it is no longer easily possible to use a table-based transition as > before. The reason is that the role of the host (server or client) also plays a > `role' in the state transition. Therefore DCCP_ACTION_FIN has also been removed. > Another difference is that the transition into DCCP_CLOSED is now after sending > the Close/CloseReq. > > Signed-off-by: Gerrit Renker <gerrit@xxxxxxxxxxxxxx> Signed-off-by: Ian McDonald <ian.mcdonald@xxxxxxxxxxx> -- Web1: http://wand.net.nz/~iam4/ Web2: http://www.jandi.co.nz Blog: http://iansblog.jandi.co.nz - 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
