2005-08-10 07:14:34 +04:00
/*
* net / dccp / input . c
2006-12-10 21:01:18 +03:00
*
2005-08-10 07:14:34 +04:00
* An implementation of the DCCP protocol
* Arnaldo Carvalho de Melo < acme @ conectiva . com . br >
*
* This program is free software ; you can redistribute it and / or
* modify it under the terms of the GNU General Public License
* as published by the Free Software Foundation ; either version
* 2 of the License , or ( at your option ) any later version .
*/
# include <linux/dccp.h>
# include <linux/skbuff.h>
# include <net/sock.h>
2005-09-18 11:17:51 +04:00
# include "ackvec.h"
2005-08-10 07:14:34 +04:00
# include "ccid.h"
# include "dccp.h"
2007-10-18 06:33:06 +04:00
/* rate-limit for syncs in reply to sequence-invalid packets; RFC 4340, 7.5.4 */
int sysctl_dccp_sync_ratelimit __read_mostly = HZ / 8 ;
2005-08-10 07:14:34 +04:00
static void dccp_fin ( struct sock * sk , struct sk_buff * skb )
{
sk - > sk_shutdown | = RCV_SHUTDOWN ;
sock_set_flag ( sk , SOCK_DONE ) ;
__skb_pull ( skb , dccp_hdr ( skb ) - > dccph_doff * 4 ) ;
__skb_queue_tail ( & sk - > sk_receive_queue , skb ) ;
skb_set_owner_r ( skb , sk ) ;
sk - > sk_data_ready ( sk , 0 ) ;
}
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
static int dccp_rcv_close ( struct sock * sk , struct sk_buff * skb )
2005-08-10 07:14:34 +04:00
{
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
int queued = 0 ;
switch ( sk - > sk_state ) {
/*
* We ignore Close when received in one of the following states :
* - CLOSED ( may be a late or duplicate packet )
* - PASSIVE_CLOSEREQ ( the peer has sent a CloseReq earlier )
* - RESPOND ( already handled by dccp_check_req )
*/
case DCCP_CLOSING :
/*
* Simultaneous - close : receiving a Close after sending one . This
* can happen if both client and server perform active - close and
* will result in an endless ping - pong of crossing and retrans -
* mitted Close packets , which only terminates when one of the
* nodes times out ( min . 64 seconds ) . Quicker convergence can be
* achieved when one of the nodes acts as tie - breaker .
* This is ok as both ends are done with data transfer and each
* end is just waiting for the other to acknowledge termination .
*/
if ( dccp_sk ( sk ) - > dccps_role ! = DCCP_ROLE_CLIENT )
break ;
/* fall through */
case DCCP_REQUESTING :
case DCCP_ACTIVE_CLOSEREQ :
dccp_send_reset ( sk , DCCP_RESET_CODE_CLOSED ) ;
dccp_done ( sk ) ;
break ;
case DCCP_OPEN :
case DCCP_PARTOPEN :
/* Give waiting application a chance to read pending data */
queued = 1 ;
dccp_fin ( sk , skb ) ;
dccp_set_state ( sk , DCCP_PASSIVE_CLOSE ) ;
/* fall through */
case DCCP_PASSIVE_CLOSE :
/*
* Retransmitted Close : we have already enqueued the first one .
*/
sk_wake_async ( sk , SOCK_WAKE_WAITD , POLL_HUP ) ;
}
return queued ;
2005-08-10 07:14:34 +04:00
}
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
static int dccp_rcv_closereq ( struct sock * sk , struct sk_buff * skb )
2005-08-10 07:14:34 +04:00
{
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
int queued = 0 ;
2005-08-10 07:14:34 +04:00
/*
* Step 7 : Check for unexpected packet types
* If ( S . is_server and P . type = = CloseReq )
* Send Sync packet acknowledging P . seqno
* Drop packet and return
*/
if ( dccp_sk ( sk ) - > dccps_role ! = DCCP_ROLE_CLIENT ) {
2005-08-17 10:10:59 +04:00
dccp_send_sync ( sk , DCCP_SKB_CB ( skb ) - > dccpd_seq , DCCP_PKT_SYNC ) ;
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
return queued ;
2005-08-10 07:14:34 +04:00
}
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
/* Step 13: process relevant Client states < CLOSEREQ */
switch ( sk - > sk_state ) {
case DCCP_REQUESTING :
dccp_send_close ( sk , 0 ) ;
2005-09-14 02:03:15 +04:00
dccp_set_state ( sk , DCCP_CLOSING ) ;
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
break ;
case DCCP_OPEN :
case DCCP_PARTOPEN :
/* Give waiting application a chance to read pending data */
queued = 1 ;
dccp_fin ( sk , skb ) ;
dccp_set_state ( sk , DCCP_PASSIVE_CLOSEREQ ) ;
/* fall through */
case DCCP_PASSIVE_CLOSEREQ :
sk_wake_async ( sk , SOCK_WAKE_WAITD , POLL_HUP ) ;
}
return queued ;
2005-08-10 07:14:34 +04:00
}
[DCCP]: Convert Reset code into socket error number
This adds support for converting the 11 currently defined Reset codes into system
error numbers, which are stored in sk_err for further interpretation.
This makes the externally visible API behaviour similar to TCP, since a client
connecting to a non-existing port will experience ECONNREFUSED.
* Code 0, Unspecified, is interpreted as non-error (0);
* Code 1, Closed (normal termination), also maps into 0;
* Code 2, Aborted, maps into "Connection reset by peer" (ECONNRESET);
* Code 3, No Connection and
Code 7, Connection Refused, map into "Connection refused" (ECONNREFUSED);
* Code 4, Packet Error, maps into "No message of desired type" (ENOMSG);
* Code 5, Option Error, maps into "Illegal byte sequence" (EILSEQ);
* Code 6, Mandatory Error, maps into "Operation not supported on transport endpoint" (EOPNOTSUPP);
* Code 8, Bad Service Code, maps into "Invalid request code" (EBADRQC);
* Code 9, Too Busy, maps into "Too many users" (EUSERS);
* Code 10, Bad Init Cookie, maps into "Invalid request descriptor" (EBADR);
* Code 11, Aggression Penalty, maps into "Quota exceeded" (EDQUOT)
which makes sense in terms of using more than the `fair share' of bandwidth.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2007-10-24 16:27:48 +04:00
static u8 dccp_reset_code_convert ( const u8 code )
{
const u8 error_code [ ] = {
[ DCCP_RESET_CODE_CLOSED ] = 0 , /* normal termination */
[ DCCP_RESET_CODE_UNSPECIFIED ] = 0 , /* nothing known */
[ DCCP_RESET_CODE_ABORTED ] = ECONNRESET ,
[ DCCP_RESET_CODE_NO_CONNECTION ] = ECONNREFUSED ,
[ DCCP_RESET_CODE_CONNECTION_REFUSED ] = ECONNREFUSED ,
[ DCCP_RESET_CODE_TOO_BUSY ] = EUSERS ,
[ DCCP_RESET_CODE_AGGRESSION_PENALTY ] = EDQUOT ,
[ DCCP_RESET_CODE_PACKET_ERROR ] = ENOMSG ,
[ DCCP_RESET_CODE_BAD_INIT_COOKIE ] = EBADR ,
[ DCCP_RESET_CODE_BAD_SERVICE_CODE ] = EBADRQC ,
[ DCCP_RESET_CODE_OPTION_ERROR ] = EILSEQ ,
[ DCCP_RESET_CODE_MANDATORY_ERROR ] = EOPNOTSUPP ,
} ;
return code > = DCCP_MAX_RESET_CODES ? 0 : error_code [ code ] ;
}
static void dccp_rcv_reset ( struct sock * sk , struct sk_buff * skb )
{
u8 err = dccp_reset_code_convert ( dccp_hdr_reset ( skb ) - > dccph_reset_code ) ;
sk - > sk_err = err ;
/* Queue the equivalent of TCP fin so that dccp_recvmsg exits the loop */
dccp_fin ( sk , skb ) ;
if ( err & & ! sock_flag ( sk , SOCK_DEAD ) )
2007-11-26 15:10:50 +03:00
sk_wake_async ( sk , SOCK_WAKE_IO , POLL_ERR ) ;
[DCCP]: Convert Reset code into socket error number
This adds support for converting the 11 currently defined Reset codes into system
error numbers, which are stored in sk_err for further interpretation.
This makes the externally visible API behaviour similar to TCP, since a client
connecting to a non-existing port will experience ECONNREFUSED.
* Code 0, Unspecified, is interpreted as non-error (0);
* Code 1, Closed (normal termination), also maps into 0;
* Code 2, Aborted, maps into "Connection reset by peer" (ECONNRESET);
* Code 3, No Connection and
Code 7, Connection Refused, map into "Connection refused" (ECONNREFUSED);
* Code 4, Packet Error, maps into "No message of desired type" (ENOMSG);
* Code 5, Option Error, maps into "Illegal byte sequence" (EILSEQ);
* Code 6, Mandatory Error, maps into "Operation not supported on transport endpoint" (EOPNOTSUPP);
* Code 8, Bad Service Code, maps into "Invalid request code" (EBADRQC);
* Code 9, Too Busy, maps into "Too many users" (EUSERS);
* Code 10, Bad Init Cookie, maps into "Invalid request descriptor" (EBADR);
* Code 11, Aggression Penalty, maps into "Quota exceeded" (EDQUOT)
which makes sense in terms of using more than the `fair share' of bandwidth.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2007-10-24 16:27:48 +04:00
dccp_time_wait ( sk , DCCP_TIME_WAIT , 0 ) ;
}
2006-03-21 08:58:56 +03:00
static void dccp_event_ack_recv ( struct sock * sk , struct sk_buff * skb )
2005-08-10 07:14:34 +04:00
{
struct dccp_sock * dp = dccp_sk ( sk ) ;
2006-03-21 09:50:58 +03:00
if ( dccp_msk ( sk ) - > dccpms_send_ack_vector )
2005-09-18 11:17:51 +04:00
dccp_ackvec_check_rcv_ackno ( dp - > dccps_hc_rx_ackvec , sk ,
DCCP_SKB_CB ( skb ) - > dccpd_ack_seq ) ;
2005-08-10 07:14:34 +04:00
}
[DCCP]: Honour and make use of shutdown option set by user
This extends the DCCP socket API by honouring any shutdown(2) option set by the user.
The behaviour is, as much as possible, made consistent with the API for TCP's shutdown.
This patch exploits the information provided by the user via the socket API to reduce
processing costs:
* if the read end is closed (SHUT_RD), it is not necessary to deliver to input CCID;
* if the write end is closed (SHUT_WR), the same idea applies, but with a difference -
as long as the TX queue has not been drained, we need to receive feedback to keep
congestion-control rates up to date. Hence SHUT_WR is honoured only after the last
packet (under congestion control) has been sent;
* although SHUT_RDWR seems nonsensical, it is nevertheless supported in the same manner
as for TCP (and agrees with test for SHUTDOWN_MASK in dccp_poll() in net/dccp/proto.c).
Furthermore, most of the code already honours the sk_shutdown flags (dccp_recvmsg() for
instance sets the read length to 0 if SHUT_RD had been called); CCID handling is now added
to this by the present patch.
There will also no longer be any delivery when the socket is in the final stages, i.e. when
one of dccp_close(), dccp_fin(), or dccp_done() has been called - which is fine since at
that stage the connection is its final stages.
Motivation and background are on http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/shutdown
A FIXME has been added to notify the other end if SHUT_RD has been set (RFC 4340, 11.7).
Note: There is a comment in inet_shutdown() in net/ipv4/af_inet.c which asks to "make
sure the socket is a TCP socket". This should probably be extended to mean
`TCP or DCCP socket' (the code is also used by UDP and raw sockets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-21 14:56:48 +03:00
static void dccp_deliver_input_to_ccids ( struct sock * sk , struct sk_buff * skb )
{
const struct dccp_sock * dp = dccp_sk ( sk ) ;
/* Don't deliver to RX CCID when node has shut down read end. */
if ( ! ( sk - > sk_shutdown & RCV_SHUTDOWN ) )
ccid_hc_rx_packet_recv ( dp - > dccps_hc_rx_ccid , sk , skb ) ;
/*
* Until the TX queue has been drained , we can not honour SHUT_WR , since
* we need received feedback as input to adjust congestion control .
*/
if ( sk - > sk_write_queue . qlen > 0 | | ! ( sk - > sk_shutdown & SEND_SHUTDOWN ) )
ccid_hc_tx_packet_recv ( dp - > dccps_hc_tx_ccid , sk , skb ) ;
}
2005-08-10 07:14:34 +04:00
static int dccp_check_seqno ( struct sock * sk , struct sk_buff * skb )
{
const struct dccp_hdr * dh = dccp_hdr ( skb ) ;
struct dccp_sock * dp = dccp_sk ( sk ) ;
2007-09-26 09:41:19 +04:00
u64 lswl , lawl , seqno = DCCP_SKB_CB ( skb ) - > dccpd_seq ,
ackno = DCCP_SKB_CB ( skb ) - > dccpd_ack_seq ;
2005-08-10 07:14:34 +04:00
/*
* Step 5 : Prepare sequence numbers for Sync
* If P . type = = Sync or P . type = = SyncAck ,
* If S . AWL < = P . ackno < = S . AWH and P . seqno > = S . SWL ,
* / * P is valid , so update sequence number variables
* accordingly . After this update , P will pass the tests
* in Step 6. A SyncAck is generated if necessary in
* Step 15 * /
* Update S . GSR , S . SWL , S . SWH
* Otherwise ,
* Drop packet and return
*/
2006-12-10 21:01:18 +03:00
if ( dh - > dccph_type = = DCCP_PKT_SYNC | |
2005-08-10 07:14:34 +04:00
dh - > dccph_type = = DCCP_PKT_SYNCACK ) {
2007-09-26 09:41:19 +04:00
if ( between48 ( ackno , dp - > dccps_awl , dp - > dccps_awh ) & &
dccp_delta_seqno ( dp - > dccps_swl , seqno ) > = 0 )
dccp_update_gsr ( sk , seqno ) ;
2005-08-10 07:14:34 +04:00
else
return - 1 ;
2005-08-17 10:10:59 +04:00
}
2007-02-09 17:24:38 +03:00
2005-08-10 07:14:34 +04:00
/*
* Step 6 : Check sequence numbers
* Let LSWL = S . SWL and LAWL = S . AWL
* If P . type = = CloseReq or P . type = = Close or P . type = = Reset ,
* LSWL : = S . GSR + 1 , LAWL : = S . GAR
* If LSWL < = P . seqno < = S . SWH
* and ( P . ackno does not exist or LAWL < = P . ackno < = S . AWH ) ,
* Update S . GSR , S . SWL , S . SWH
* If P . type ! = Sync ,
* Update S . GAR
*/
2005-08-17 10:10:59 +04:00
lswl = dp - > dccps_swl ;
lawl = dp - > dccps_awl ;
if ( dh - > dccph_type = = DCCP_PKT_CLOSEREQ | |
2005-08-19 04:12:02 +04:00
dh - > dccph_type = = DCCP_PKT_CLOSE | |
dh - > dccph_type = = DCCP_PKT_RESET ) {
2007-09-26 09:41:19 +04:00
lswl = ADD48 ( dp - > dccps_gsr , 1 ) ;
2005-08-10 07:14:34 +04:00
lawl = dp - > dccps_gar ;
}
2007-09-26 09:41:19 +04:00
if ( between48 ( seqno , lswl , dp - > dccps_swh ) & &
( ackno = = DCCP_PKT_WITHOUT_ACK_SEQ | |
between48 ( ackno , lawl , dp - > dccps_awh ) ) ) {
dccp_update_gsr ( sk , seqno ) ;
2005-08-10 07:14:34 +04:00
if ( dh - > dccph_type ! = DCCP_PKT_SYNC & &
2007-09-26 09:41:19 +04:00
( ackno ! = DCCP_PKT_WITHOUT_ACK_SEQ ) )
dp - > dccps_gar = ackno ;
2005-08-10 07:14:34 +04:00
} else {
2007-09-26 18:31:49 +04:00
unsigned long now = jiffies ;
/*
* Step 6 : Check sequence numbers
* Otherwise ,
* If P . type = = Reset ,
* Send Sync packet acknowledging S . GSR
* Otherwise ,
* Send Sync packet acknowledging P . seqno
* Drop packet and return
*
* These Syncs are rate - limited as per RFC 4340 , 7.5 .4 :
* at most 1 / ( dccp_sync_rate_limit * HZ ) Syncs per second .
*/
if ( time_before ( now , ( dp - > dccps_rate_last +
sysctl_dccp_sync_ratelimit ) ) )
return 0 ;
2006-11-20 23:39:23 +03:00
DCCP_WARN ( " DCCP: Step 6 failed for %s packet, "
" (LSWL(%llu) <= P.seqno(%llu) <= S.SWH(%llu)) and "
" (P.ackno %s or LAWL(%llu) <= P.ackno(%llu) <= S.AWH(%llu), "
" sending SYNC... \n " , dccp_packet_name ( dh - > dccph_type ) ,
2007-09-26 09:41:19 +04:00
( unsigned long long ) lswl , ( unsigned long long ) seqno ,
2006-11-20 23:39:23 +03:00
( unsigned long long ) dp - > dccps_swh ,
2007-09-26 09:41:19 +04:00
( ackno = = DCCP_PKT_WITHOUT_ACK_SEQ ) ? " doesn't exist "
: " exists " ,
( unsigned long long ) lawl , ( unsigned long long ) ackno ,
2006-11-20 23:39:23 +03:00
( unsigned long long ) dp - > dccps_awh ) ;
2007-09-26 18:31:49 +04:00
dp - > dccps_rate_last = now ;
2007-09-26 09:41:56 +04:00
if ( dh - > dccph_type = = DCCP_PKT_RESET )
seqno = dp - > dccps_gsr ;
2007-09-26 09:41:19 +04:00
dccp_send_sync ( sk , seqno , DCCP_PKT_SYNC ) ;
2005-08-10 07:14:34 +04:00
return - 1 ;
}
return 0 ;
}
2006-03-21 08:58:56 +03:00
static int __dccp_rcv_established ( struct sock * sk , struct sk_buff * skb ,
const struct dccp_hdr * dh , const unsigned len )
2005-08-10 07:14:34 +04:00
{
struct dccp_sock * dp = dccp_sk ( sk ) ;
switch ( dccp_hdr ( skb ) - > dccph_type ) {
case DCCP_PKT_DATAACK :
case DCCP_PKT_DATA :
/*
[DCCP]: Honour and make use of shutdown option set by user
This extends the DCCP socket API by honouring any shutdown(2) option set by the user.
The behaviour is, as much as possible, made consistent with the API for TCP's shutdown.
This patch exploits the information provided by the user via the socket API to reduce
processing costs:
* if the read end is closed (SHUT_RD), it is not necessary to deliver to input CCID;
* if the write end is closed (SHUT_WR), the same idea applies, but with a difference -
as long as the TX queue has not been drained, we need to receive feedback to keep
congestion-control rates up to date. Hence SHUT_WR is honoured only after the last
packet (under congestion control) has been sent;
* although SHUT_RDWR seems nonsensical, it is nevertheless supported in the same manner
as for TCP (and agrees with test for SHUTDOWN_MASK in dccp_poll() in net/dccp/proto.c).
Furthermore, most of the code already honours the sk_shutdown flags (dccp_recvmsg() for
instance sets the read length to 0 if SHUT_RD had been called); CCID handling is now added
to this by the present patch.
There will also no longer be any delivery when the socket is in the final stages, i.e. when
one of dccp_close(), dccp_fin(), or dccp_done() has been called - which is fine since at
that stage the connection is its final stages.
Motivation and background are on http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/shutdown
A FIXME has been added to notify the other end if SHUT_RD has been set (RFC 4340, 11.7).
Note: There is a comment in inet_shutdown() in net/ipv4/af_inet.c which asks to "make
sure the socket is a TCP socket". This should probably be extended to mean
`TCP or DCCP socket' (the code is also used by UDP and raw sockets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-21 14:56:48 +03:00
* FIXME : schedule DATA_DROPPED ( RFC 4340 , 11.7 .2 ) if and when
* - sk_shutdown = = RCV_SHUTDOWN , use Code 1 , " Not Listening "
* - sk_receive_queue is full , use Code 2 , " Receive Buffer "
2005-08-10 07:14:34 +04:00
*/
__skb_pull ( skb , dh - > dccph_doff * 4 ) ;
__skb_queue_tail ( & sk - > sk_receive_queue , skb ) ;
skb_set_owner_r ( skb , sk ) ;
sk - > sk_data_ready ( sk , 0 ) ;
return 0 ;
case DCCP_PKT_ACK :
goto discard ;
case DCCP_PKT_RESET :
/*
* Step 9 : Process Reset
* If P . type = = Reset ,
* Tear down connection
* S . state : = TIMEWAIT
* Set TIMEWAIT timer
* Drop packet and return
[DCCP]: Convert Reset code into socket error number
This adds support for converting the 11 currently defined Reset codes into system
error numbers, which are stored in sk_err for further interpretation.
This makes the externally visible API behaviour similar to TCP, since a client
connecting to a non-existing port will experience ECONNREFUSED.
* Code 0, Unspecified, is interpreted as non-error (0);
* Code 1, Closed (normal termination), also maps into 0;
* Code 2, Aborted, maps into "Connection reset by peer" (ECONNRESET);
* Code 3, No Connection and
Code 7, Connection Refused, map into "Connection refused" (ECONNREFUSED);
* Code 4, Packet Error, maps into "No message of desired type" (ENOMSG);
* Code 5, Option Error, maps into "Illegal byte sequence" (EILSEQ);
* Code 6, Mandatory Error, maps into "Operation not supported on transport endpoint" (EOPNOTSUPP);
* Code 8, Bad Service Code, maps into "Invalid request code" (EBADRQC);
* Code 9, Too Busy, maps into "Too many users" (EUSERS);
* Code 10, Bad Init Cookie, maps into "Invalid request descriptor" (EBADR);
* Code 11, Aggression Penalty, maps into "Quota exceeded" (EDQUOT)
which makes sense in terms of using more than the `fair share' of bandwidth.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2007-10-24 16:27:48 +04:00
*/
dccp_rcv_reset ( sk , skb ) ;
2005-08-10 07:14:34 +04:00
return 0 ;
case DCCP_PKT_CLOSEREQ :
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
if ( dccp_rcv_closereq ( sk , skb ) )
return 0 ;
2005-08-10 07:14:34 +04:00
goto discard ;
case DCCP_PKT_CLOSE :
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
if ( dccp_rcv_close ( sk , skb ) )
return 0 ;
goto discard ;
2005-08-10 07:14:34 +04:00
case DCCP_PKT_REQUEST :
2006-12-10 21:01:18 +03:00
/* Step 7
* or ( S . is_server and P . type = = Response )
2005-08-10 07:14:34 +04:00
* or ( S . is_client and P . type = = Request )
* or ( S . state > = OPEN and P . type = = Request
* and P . seqno > = S . OSR )
* or ( S . state > = OPEN and P . type = = Response
* and P . seqno > = S . OSR )
* or ( S . state = = RESPOND and P . type = = Data ) ,
* Send Sync packet acknowledging P . seqno
* Drop packet and return
*/
if ( dp - > dccps_role ! = DCCP_ROLE_LISTEN )
goto send_sync ;
goto check_seq ;
case DCCP_PKT_RESPONSE :
if ( dp - > dccps_role ! = DCCP_ROLE_CLIENT )
goto send_sync ;
check_seq :
2007-03-20 19:08:19 +03:00
if ( dccp_delta_seqno ( dp - > dccps_osr ,
DCCP_SKB_CB ( skb ) - > dccpd_seq ) > = 0 ) {
2005-08-10 07:14:34 +04:00
send_sync :
2005-08-17 10:10:59 +04:00
dccp_send_sync ( sk , DCCP_SKB_CB ( skb ) - > dccpd_seq ,
DCCP_PKT_SYNC ) ;
2005-08-10 07:14:34 +04:00
}
break ;
2005-08-17 10:10:59 +04:00
case DCCP_PKT_SYNC :
dccp_send_sync ( sk , DCCP_SKB_CB ( skb ) - > dccpd_seq ,
DCCP_PKT_SYNCACK ) ;
/*
2006-10-25 03:17:51 +04:00
* From RFC 4340 , sec . 5.7
2005-08-17 10:10:59 +04:00
*
* As with DCCP - Ack packets , DCCP - Sync and DCCP - SyncAck packets
* MAY have non - zero - length application data areas , whose
2006-10-25 03:17:51 +04:00
* contents receivers MUST ignore .
2005-08-17 10:10:59 +04:00
*/
goto discard ;
2005-08-10 07:14:34 +04:00
}
DCCP_INC_STATS_BH ( DCCP_MIB_INERRS ) ;
discard :
__kfree_skb ( skb ) ;
return 0 ;
}
2006-01-04 01:25:17 +03:00
int dccp_rcv_established ( struct sock * sk , struct sk_buff * skb ,
const struct dccp_hdr * dh , const unsigned len )
{
struct dccp_sock * dp = dccp_sk ( sk ) ;
if ( dccp_check_seqno ( sk , skb ) )
goto discard ;
if ( dccp_parse_options ( sk , skb ) )
goto discard ;
if ( DCCP_SKB_CB ( skb ) - > dccpd_ack_seq ! = DCCP_PKT_WITHOUT_ACK_SEQ )
dccp_event_ack_recv ( sk , skb ) ;
2006-03-21 09:50:58 +03:00
if ( dccp_msk ( sk ) - > dccpms_send_ack_vector & &
2006-01-04 01:25:17 +03:00
dccp_ackvec_add ( dp - > dccps_hc_rx_ackvec , sk ,
DCCP_SKB_CB ( skb ) - > dccpd_seq ,
DCCP_ACKVEC_STATE_RECEIVED ) )
goto discard ;
[DCCP]: Honour and make use of shutdown option set by user
This extends the DCCP socket API by honouring any shutdown(2) option set by the user.
The behaviour is, as much as possible, made consistent with the API for TCP's shutdown.
This patch exploits the information provided by the user via the socket API to reduce
processing costs:
* if the read end is closed (SHUT_RD), it is not necessary to deliver to input CCID;
* if the write end is closed (SHUT_WR), the same idea applies, but with a difference -
as long as the TX queue has not been drained, we need to receive feedback to keep
congestion-control rates up to date. Hence SHUT_WR is honoured only after the last
packet (under congestion control) has been sent;
* although SHUT_RDWR seems nonsensical, it is nevertheless supported in the same manner
as for TCP (and agrees with test for SHUTDOWN_MASK in dccp_poll() in net/dccp/proto.c).
Furthermore, most of the code already honours the sk_shutdown flags (dccp_recvmsg() for
instance sets the read length to 0 if SHUT_RD had been called); CCID handling is now added
to this by the present patch.
There will also no longer be any delivery when the socket is in the final stages, i.e. when
one of dccp_close(), dccp_fin(), or dccp_done() has been called - which is fine since at
that stage the connection is its final stages.
Motivation and background are on http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/shutdown
A FIXME has been added to notify the other end if SHUT_RD has been set (RFC 4340, 11.7).
Note: There is a comment in inet_shutdown() in net/ipv4/af_inet.c which asks to "make
sure the socket is a TCP socket". This should probably be extended to mean
`TCP or DCCP socket' (the code is also used by UDP and raw sockets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-21 14:56:48 +03:00
dccp_deliver_input_to_ccids ( sk , skb ) ;
2006-01-04 01:25:17 +03:00
return __dccp_rcv_established ( sk , skb , dh , len ) ;
discard :
__kfree_skb ( skb ) ;
return 0 ;
}
2005-12-14 10:24:16 +03:00
EXPORT_SYMBOL_GPL ( dccp_rcv_established ) ;
2005-08-10 07:14:34 +04:00
static int dccp_rcv_request_sent_state_process ( struct sock * sk ,
struct sk_buff * skb ,
const struct dccp_hdr * dh ,
const unsigned len )
{
2006-12-10 21:01:18 +03:00
/*
2005-08-10 07:14:34 +04:00
* Step 4 : Prepare sequence numbers in REQUEST
* If S . state = = REQUEST ,
* If ( P . type = = Response or P . type = = Reset )
* and S . AWL < = P . ackno < = S . AWH ,
* / * Set sequence number variables corresponding to the
* other endpoint , so P will pass the tests in Step 6 * /
* Set S . GSR , S . ISR , S . SWL , S . SWH
* / * Response processing continues in Step 10 ; Reset
* processing continues in Step 9 * /
*/
if ( dh - > dccph_type = = DCCP_PKT_RESPONSE ) {
const struct inet_connection_sock * icsk = inet_csk ( sk ) ;
struct dccp_sock * dp = dccp_sk ( sk ) ;
2007-09-26 09:40:44 +04:00
long tstamp = dccp_timestamp ( ) ;
2005-08-10 07:14:34 +04:00
/* Stop the REQUEST timer */
inet_csk_clear_xmit_timer ( sk , ICSK_TIME_RETRANS ) ;
BUG_TRAP ( sk - > sk_send_head ! = NULL ) ;
__kfree_skb ( sk - > sk_send_head ) ;
sk - > sk_send_head = NULL ;
2005-08-14 03:34:54 +04:00
if ( ! between48 ( DCCP_SKB_CB ( skb ) - > dccpd_ack_seq ,
dp - > dccps_awl , dp - > dccps_awh ) ) {
dccp_pr_debug ( " invalid ackno: S.AWL=%llu, "
" P.ackno=%llu, S.AWH=%llu \n " ,
( unsigned long long ) dp - > dccps_awl ,
( unsigned long long ) DCCP_SKB_CB ( skb ) - > dccpd_ack_seq ,
( unsigned long long ) dp - > dccps_awh ) ;
2005-08-10 07:14:34 +04:00
goto out_invalid_packet ;
}
2006-01-04 01:25:49 +03:00
[DCCP]: Initial feature negotiation implementation
Still needs more work, but boots and doesn't crashes, even
does some negotiation!
18:38:52.174934 127.0.0.1.43458 > 127.0.0.1.5001: request <change_l ack_ratio 2, change_r ccid 2, change_l ccid 2>
18:38:52.218526 127.0.0.1.5001 > 127.0.0.1.43458: response <nop, nop, change_l ack_ratio 2, confirm_r ccid 2 2, confirm_l ccid 2 2, confirm_r ack_ratio 2>
18:38:52.185398 127.0.0.1.43458 > 127.0.0.1.5001: <nop, confirm_r ack_ratio 2, ack_vector0 0x00, elapsed_time 212>
:-)
Signed-off-by: Andrea Bittau <a.bittau@cs.ucl.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2006-03-21 04:43:56 +03:00
if ( dccp_parse_options ( sk , skb ) )
goto out_invalid_packet ;
2007-09-26 09:40:44 +04:00
/* Obtain usec RTT sample from SYN exchange (used by CCID 3) */
if ( likely ( dp - > dccps_options_received . dccpor_timestamp_echo ) )
dp - > dccps_syn_rtt = dccp_sample_rtt ( sk , 10 * ( tstamp -
dp - > dccps_options_received . dccpor_timestamp_echo ) ) ;
2007-03-20 21:27:17 +03:00
2007-02-09 17:24:38 +03:00
if ( dccp_msk ( sk ) - > dccpms_send_ack_vector & &
dccp_ackvec_add ( dp - > dccps_hc_rx_ackvec , sk ,
DCCP_SKB_CB ( skb ) - > dccpd_seq ,
DCCP_ACKVEC_STATE_RECEIVED ) )
goto out_invalid_packet ; /* FIXME: change error code */
2005-08-10 07:14:34 +04:00
dp - > dccps_isr = DCCP_SKB_CB ( skb ) - > dccpd_seq ;
2005-08-21 12:36:45 +04:00
dccp_update_gsr ( sk , dp - > dccps_isr ) ;
/*
* SWL and AWL are initially adjusted so that they are not less than
* the initial Sequence Numbers received and sent , respectively :
* SWL : = max ( GSR + 1 - floor ( W / 4 ) , ISR ) ,
* AWL : = max ( GSS - W ' + 1 , ISS ) .
* These adjustments MUST be applied only at the beginning of the
* connection .
*
* AWL was adjusted in dccp_v4_connect - acme
*/
dccp_set_seqno ( & dp - > dccps_swl ,
max48 ( dp - > dccps_swl , dp - > dccps_isr ) ) ;
2005-08-10 07:14:34 +04:00
2005-12-14 10:26:10 +03:00
dccp_sync_mss ( sk , icsk - > icsk_pmtu_cookie ) ;
2005-08-10 07:14:34 +04:00
/*
* Step 10 : Process REQUEST state ( second part )
* If S . state = = REQUEST ,
2005-08-14 03:34:54 +04:00
* / * If we get here , P is a valid Response from the
* server ( see Step 4 ) , and we should move to
* PARTOPEN state . PARTOPEN means send an Ack ,
* don ' t send Data packets , retransmit Acks
* periodically , and always include any Init Cookie
* from the Response * /
2005-08-10 07:14:34 +04:00
* S . state : = PARTOPEN
* Set PARTOPEN timer
2006-12-10 21:01:18 +03:00
* Continue with S . state = = PARTOPEN
2005-08-14 03:34:54 +04:00
* / * Step 12 will send the Ack completing the
* three - way handshake * /
2005-08-10 07:14:34 +04:00
*/
dccp_set_state ( sk , DCCP_PARTOPEN ) ;
/* Make sure socket is routed, for correct metrics. */
2005-12-14 10:16:16 +03:00
icsk - > icsk_af_ops - > rebuild_header ( sk ) ;
2005-08-10 07:14:34 +04:00
if ( ! sock_flag ( sk , SOCK_DEAD ) ) {
sk - > sk_state_change ( sk ) ;
2007-11-26 15:10:50 +03:00
sk_wake_async ( sk , SOCK_WAKE_IO , POLL_OUT ) ;
2005-08-10 07:14:34 +04:00
}
if ( sk - > sk_write_pending | | icsk - > icsk_ack . pingpong | |
icsk - > icsk_accept_queue . rskq_defer_accept ) {
/* Save one ACK. Data will be ready after
* several ticks , if write_pending is set .
*
* It may be deleted , but with this feature tcpdumps
* look so _wonderfully_ clever , that I was not able
* to stand against the temptation 8 ) - - ANK
*/
/*
* OK , in DCCP we can as well do a similar trick , its
* even in the draft , but there is no need for us to
* schedule an ack here , as dccp_sendmsg does this for
* us , also stated in the draft . - acme
*/
__kfree_skb ( skb ) ;
return 0 ;
2006-12-10 21:01:18 +03:00
}
2005-08-10 07:14:34 +04:00
dccp_send_ack ( sk ) ;
return - 1 ;
}
out_invalid_packet :
2005-09-17 03:58:33 +04:00
/* dccp_v4_do_rcv will send a reset */
DCCP_SKB_CB ( skb ) - > dccpd_reset_code = DCCP_RESET_CODE_PACKET_ERROR ;
2006-12-10 21:01:18 +03:00
return 1 ;
2005-08-10 07:14:34 +04:00
}
static int dccp_rcv_respond_partopen_state_process ( struct sock * sk ,
struct sk_buff * skb ,
const struct dccp_hdr * dh ,
const unsigned len )
{
int queued = 0 ;
switch ( dh - > dccph_type ) {
case DCCP_PKT_RESET :
inet_csk_clear_xmit_timer ( sk , ICSK_TIME_DACK ) ;
break ;
2005-10-11 08:25:00 +04:00
case DCCP_PKT_DATA :
if ( sk - > sk_state = = DCCP_RESPOND )
break ;
2005-08-10 07:14:34 +04:00
case DCCP_PKT_DATAACK :
case DCCP_PKT_ACK :
/*
2005-08-14 03:34:54 +04:00
* FIXME : we should be reseting the PARTOPEN ( DELACK ) timer
* here but only if we haven ' t used the DELACK timer for
* something else , like sending a delayed ack for a TIMESTAMP
* echo , etc , for now were not clearing it , sending an extra
* ACK when there is nothing else to do in DELACK is not a big
* deal after all .
2005-08-10 07:14:34 +04:00
*/
/* Stop the PARTOPEN timer */
if ( sk - > sk_state = = DCCP_PARTOPEN )
inet_csk_clear_xmit_timer ( sk , ICSK_TIME_DACK ) ;
dccp_sk ( sk ) - > dccps_osr = DCCP_SKB_CB ( skb ) - > dccpd_seq ;
dccp_set_state ( sk , DCCP_OPEN ) ;
2005-10-11 08:25:00 +04:00
if ( dh - > dccph_type = = DCCP_PKT_DATAACK | |
dh - > dccph_type = = DCCP_PKT_DATA ) {
2006-01-04 01:25:17 +03:00
__dccp_rcv_established ( sk , skb , dh , len ) ;
2005-08-14 03:34:54 +04:00
queued = 1 ; /* packet was queued
2006-01-04 01:25:17 +03:00
( by __dccp_rcv_established ) */
2005-08-10 07:14:34 +04:00
}
break ;
}
return queued ;
}
int dccp_rcv_state_process ( struct sock * sk , struct sk_buff * skb ,
struct dccp_hdr * dh , unsigned len )
{
struct dccp_sock * dp = dccp_sk ( sk ) ;
2005-09-17 03:58:33 +04:00
struct dccp_skb_cb * dcb = DCCP_SKB_CB ( skb ) ;
2005-08-10 07:14:34 +04:00
const int old_state = sk - > sk_state ;
int queued = 0 ;
2005-08-14 03:36:01 +04:00
/*
* Step 3 : Process LISTEN state
*
* If S . state = = LISTEN ,
2006-11-10 21:29:14 +03:00
* If P . type = = Request or P contains a valid Init Cookie option ,
* ( * Must scan the packet ' s options to check for Init
* Cookies . Only Init Cookies are processed here ,
* however ; other options are processed in Step 8. This
* scan need only be performed if the endpoint uses Init
* Cookies * )
* ( * Generate a new socket and switch to that socket * )
* Set S : = new socket for this port pair
* S . state = RESPOND
* Choose S . ISS ( initial seqno ) or set from Init Cookies
* Initialize S . GAR : = S . ISS
* Set S . ISR , S . GSR , S . SWL , S . SWH from packet or Init
* Cookies Continue with S . state = = RESPOND
* ( * A Response packet will be generated in Step 11 * )
* Otherwise ,
* Generate Reset ( No Connection ) unless P . type = = Reset
* Drop packet and return
2005-08-14 03:36:01 +04:00
*/
if ( sk - > sk_state = = DCCP_LISTEN ) {
if ( dh - > dccph_type = = DCCP_PKT_REQUEST ) {
2005-12-14 10:16:16 +03:00
if ( inet_csk ( sk ) - > icsk_af_ops - > conn_request ( sk ,
skb ) < 0 )
2005-08-14 03:36:01 +04:00
return 1 ;
/* FIXME: do congestion control initialization */
goto discard ;
}
if ( dh - > dccph_type = = DCCP_PKT_RESET )
goto discard ;
2005-09-17 03:58:33 +04:00
/* Caller (dccp_v4_do_rcv) will send Reset */
dcb - > dccpd_reset_code = DCCP_RESET_CODE_NO_CONNECTION ;
2005-08-14 03:36:01 +04:00
return 1 ;
}
if ( sk - > sk_state ! = DCCP_REQUESTING ) {
2005-08-10 07:14:34 +04:00
if ( dccp_check_seqno ( sk , skb ) )
goto discard ;
/*
* Step 8 : Process options and mark acknowledgeable
*/
if ( dccp_parse_options ( sk , skb ) )
goto discard ;
2005-09-17 03:58:33 +04:00
if ( dcb - > dccpd_ack_seq ! = DCCP_PKT_WITHOUT_ACK_SEQ )
2005-08-10 07:14:34 +04:00
dccp_event_ack_recv ( sk , skb ) ;
2006-12-10 21:01:18 +03:00
if ( dccp_msk ( sk ) - > dccpms_send_ack_vector & &
2005-09-18 11:17:51 +04:00
dccp_ackvec_add ( dp - > dccps_hc_rx_ackvec , sk ,
2006-12-10 21:01:18 +03:00
DCCP_SKB_CB ( skb ) - > dccpd_seq ,
DCCP_ACKVEC_STATE_RECEIVED ) )
goto discard ;
2006-01-04 01:26:15 +03:00
[DCCP]: Honour and make use of shutdown option set by user
This extends the DCCP socket API by honouring any shutdown(2) option set by the user.
The behaviour is, as much as possible, made consistent with the API for TCP's shutdown.
This patch exploits the information provided by the user via the socket API to reduce
processing costs:
* if the read end is closed (SHUT_RD), it is not necessary to deliver to input CCID;
* if the write end is closed (SHUT_WR), the same idea applies, but with a difference -
as long as the TX queue has not been drained, we need to receive feedback to keep
congestion-control rates up to date. Hence SHUT_WR is honoured only after the last
packet (under congestion control) has been sent;
* although SHUT_RDWR seems nonsensical, it is nevertheless supported in the same manner
as for TCP (and agrees with test for SHUTDOWN_MASK in dccp_poll() in net/dccp/proto.c).
Furthermore, most of the code already honours the sk_shutdown flags (dccp_recvmsg() for
instance sets the read length to 0 if SHUT_RD had been called); CCID handling is now added
to this by the present patch.
There will also no longer be any delivery when the socket is in the final stages, i.e. when
one of dccp_close(), dccp_fin(), or dccp_done() has been called - which is fine since at
that stage the connection is its final stages.
Motivation and background are on http://www.erg.abdn.ac.uk/users/gerrit/dccp/notes/shutdown
A FIXME has been added to notify the other end if SHUT_RD has been set (RFC 4340, 11.7).
Note: There is a comment in inet_shutdown() in net/ipv4/af_inet.c which asks to "make
sure the socket is a TCP socket". This should probably be extended to mean
`TCP or DCCP socket' (the code is also used by UDP and raw sockets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-21 14:56:48 +03:00
dccp_deliver_input_to_ccids ( sk , skb ) ;
2005-08-10 07:14:34 +04:00
}
/*
* Step 9 : Process Reset
* If P . type = = Reset ,
* Tear down connection
* S . state : = TIMEWAIT
* Set TIMEWAIT timer
* Drop packet and return
*/
if ( dh - > dccph_type = = DCCP_PKT_RESET ) {
[DCCP]: Convert Reset code into socket error number
This adds support for converting the 11 currently defined Reset codes into system
error numbers, which are stored in sk_err for further interpretation.
This makes the externally visible API behaviour similar to TCP, since a client
connecting to a non-existing port will experience ECONNREFUSED.
* Code 0, Unspecified, is interpreted as non-error (0);
* Code 1, Closed (normal termination), also maps into 0;
* Code 2, Aborted, maps into "Connection reset by peer" (ECONNRESET);
* Code 3, No Connection and
Code 7, Connection Refused, map into "Connection refused" (ECONNREFUSED);
* Code 4, Packet Error, maps into "No message of desired type" (ENOMSG);
* Code 5, Option Error, maps into "Illegal byte sequence" (EILSEQ);
* Code 6, Mandatory Error, maps into "Operation not supported on transport endpoint" (EOPNOTSUPP);
* Code 8, Bad Service Code, maps into "Invalid request code" (EBADRQC);
* Code 9, Too Busy, maps into "Too many users" (EUSERS);
* Code 10, Bad Init Cookie, maps into "Invalid request descriptor" (EBADR);
* Code 11, Aggression Penalty, maps into "Quota exceeded" (EDQUOT)
which makes sense in terms of using more than the `fair share' of bandwidth.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
2007-10-24 16:27:48 +04:00
dccp_rcv_reset ( sk , skb ) ;
2005-08-10 07:14:34 +04:00
return 0 ;
/*
* Step 7 : Check for unexpected packet types
2007-11-28 17:06:04 +03:00
* If ( S . is_server and P . type = = Response )
2005-08-10 07:14:34 +04:00
* or ( S . is_client and P . type = = Request )
* or ( S . state = = RESPOND and P . type = = Data ) ,
* Send Sync packet acknowledging P . seqno
* Drop packet and return
*/
} else if ( ( dp - > dccps_role ! = DCCP_ROLE_CLIENT & &
2007-11-28 17:06:04 +03:00
dh - > dccph_type = = DCCP_PKT_RESPONSE ) | |
2005-08-10 07:14:34 +04:00
( dp - > dccps_role = = DCCP_ROLE_CLIENT & &
dh - > dccph_type = = DCCP_PKT_REQUEST ) | |
2005-08-14 03:34:54 +04:00
( sk - > sk_state = = DCCP_RESPOND & &
dh - > dccph_type = = DCCP_PKT_DATA ) ) {
2005-09-17 03:58:33 +04:00
dccp_send_sync ( sk , dcb - > dccpd_seq , DCCP_PKT_SYNC ) ;
2005-08-10 07:14:34 +04:00
goto discard ;
2005-08-24 08:50:06 +04:00
} else if ( dh - > dccph_type = = DCCP_PKT_CLOSEREQ ) {
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
if ( dccp_rcv_closereq ( sk , skb ) )
return 0 ;
2005-08-24 08:50:06 +04:00
goto discard ;
} else if ( dh - > dccph_type = = DCCP_PKT_CLOSE ) {
[DCCP]: Integrate state transitions for passive-close
This adds the necessary state transitions for the two forms of passive-close
* PASSIVE_CLOSE - which is entered when a host receives a Close;
* PASSIVE_CLOSEREQ - which is entered when a client receives a CloseReq.
Here is a detailed account of what the patch does in each state.
1) Receiving CloseReq
The pseudo-code in 8.5 says:
Step 13: Process CloseReq
If P.type == CloseReq and S.state < CLOSEREQ,
Generate Close
S.state := CLOSING
Set CLOSING timer.
This means we need to address what to do in CLOSED, LISTEN, REQUEST, RESPOND, PARTOPEN, and OPEN.
* CLOSED: silently ignore - it may be a late or duplicate CloseReq;
* LISTEN/RESPOND: will not appear, since Step 7 is performed first (we know we are the client);
* REQUEST: perform Step 13 directly (no need to enqueue packet);
* OPEN/PARTOPEN: enter PASSIVE_CLOSEREQ so that the application has a chance to process unread data.
When already in PASSIVE_CLOSEREQ, no second CloseReq is enqueued. In any other state, the CloseReq is ignored.
I think that this offers some robustness against rare and pathological cases: e.g. a simultaneous close where
the client sends a Close and the server a CloseReq. The client will then be retransmitting its Close until it
gets the Reset, so ignoring the CloseReq while in state CLOSING is sane.
2) Receiving Close
The code below from 8.5 is unconditional.
Step 14: Process Close
If P.type == Close,
Generate Reset(Closed)
Tear down connection
Drop packet and return
Thus we need to consider all states:
* CLOSED: silently ignore, since this can happen when a retransmitted or late Close arrives;
* LISTEN: dccp_rcv_state_process() will generate a Reset ("No Connection");
* REQUEST: perform Step 14 directly (no need to enqueue packet);
* RESPOND: dccp_check_req() will generate a Reset ("Packet Error") -- left it at that;
* OPEN/PARTOPEN: enter PASSIVE_CLOSE so that application has a chance to process unread data;
* CLOSEREQ: server performed active-close -- perform Step 14;
* CLOSING: simultaneous-close: use a tie-breaker to avoid message ping-pong (see comment);
* PASSIVE_CLOSEREQ: ignore - the peer has a bug (sending first a CloseReq and now a Close);
* TIMEWAIT: packet is ignored.
Note that the condition of receiving a packet in state CLOSED here is different from the condition "there
is no socket for such a connection": the socket still exists, but its state indicates it is unusable.
Last, dccp_finish_passive_close sets either DCCP_CLOSED or DCCP_CLOSING = TCP_CLOSING, so that
sk_stream_wait_close() will wait for the final Reset (which will trigger CLOSING => CLOSED).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2007-11-28 16:59:48 +03:00
if ( dccp_rcv_close ( sk , skb ) )
return 0 ;
goto discard ;
2005-08-10 07:14:34 +04:00
}
switch ( sk - > sk_state ) {
case DCCP_CLOSED :
2005-09-17 03:58:33 +04:00
dcb - > dccpd_reset_code = DCCP_RESET_CODE_NO_CONNECTION ;
2005-08-10 07:14:34 +04:00
return 1 ;
case DCCP_REQUESTING :
/* FIXME: do congestion control initialization */
queued = dccp_rcv_request_sent_state_process ( sk , skb , dh , len ) ;
if ( queued > = 0 )
return queued ;
__kfree_skb ( skb ) ;
return 0 ;
case DCCP_RESPOND :
case DCCP_PARTOPEN :
2005-08-14 03:34:54 +04:00
queued = dccp_rcv_respond_partopen_state_process ( sk , skb ,
dh , len ) ;
2005-08-10 07:14:34 +04:00
break ;
}
2005-08-14 03:34:54 +04:00
if ( dh - > dccph_type = = DCCP_PKT_ACK | |
dh - > dccph_type = = DCCP_PKT_DATAACK ) {
2005-08-10 07:14:34 +04:00
switch ( old_state ) {
case DCCP_PARTOPEN :
sk - > sk_state_change ( sk ) ;
2007-11-26 15:10:50 +03:00
sk_wake_async ( sk , SOCK_WAKE_IO , POLL_OUT ) ;
2005-08-10 07:14:34 +04:00
break ;
}
2007-09-26 17:30:05 +04:00
} else if ( unlikely ( dh - > dccph_type = = DCCP_PKT_SYNC ) ) {
dccp_send_sync ( sk , dcb - > dccpd_seq , DCCP_PKT_SYNCACK ) ;
goto discard ;
2005-08-10 07:14:34 +04:00
}
2006-12-10 21:01:18 +03:00
if ( ! queued ) {
2005-08-10 07:14:34 +04:00
discard :
__kfree_skb ( skb ) ;
}
return 0 ;
}
2005-12-14 10:24:16 +03:00
EXPORT_SYMBOL_GPL ( dccp_rcv_state_process ) ;
2007-03-20 21:23:18 +03:00
/**
2007-09-26 09:40:44 +04:00
* dccp_sample_rtt - Validate and finalise computation of RTT sample
* @ delta : number of microseconds between packet and acknowledgment
* The routine is kept generic to work in different contexts . It should be
* called immediately when the ACK used for the RTT sample arrives .
2007-03-20 21:23:18 +03:00
*/
2007-09-26 09:40:44 +04:00
u32 dccp_sample_rtt ( struct sock * sk , long delta )
2007-03-20 21:23:18 +03:00
{
2007-09-26 09:40:44 +04:00
/* dccpor_elapsed_time is either zeroed out or set and > 0 */
delta - = dccp_sk ( sk ) - > dccps_options_received . dccpor_elapsed_time * 10 ;
2007-03-20 21:23:18 +03:00
if ( unlikely ( delta < = 0 ) ) {
2007-09-26 09:40:44 +04:00
DCCP_WARN ( " unusable RTT sample %ld, using min \n " , delta ) ;
2007-03-20 21:23:18 +03:00
return DCCP_SANE_RTT_MIN ;
}
2007-09-26 09:40:44 +04:00
if ( unlikely ( delta > DCCP_SANE_RTT_MAX ) ) {
DCCP_WARN ( " RTT sample %ld too large, using max \n " , delta ) ;
2007-03-20 21:23:18 +03:00
return DCCP_SANE_RTT_MAX ;
}
return delta ;
}
EXPORT_SYMBOL_GPL ( dccp_sample_rtt ) ;
