2005-08-09 23:14:34 -04:00
|
|
|
/*
|
|
|
|
* net/dccp/output.c
|
2006-12-10 13:01:18 -05:00
|
|
|
*
|
2005-08-09 23: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>
|
2005-10-29 20:20:59 -04:00
|
|
|
#include <linux/kernel.h>
|
2005-08-09 23:14:34 -04:00
|
|
|
#include <linux/skbuff.h>
|
|
|
|
|
2005-12-26 23:43:12 -05:00
|
|
|
#include <net/inet_sock.h>
|
2005-08-09 23:14:34 -04:00
|
|
|
#include <net/sock.h>
|
|
|
|
|
2005-09-18 03:17:51 -04:00
|
|
|
#include "ackvec.h"
|
2005-08-09 23:14:34 -04:00
|
|
|
#include "ccid.h"
|
|
|
|
#include "dccp.h"
|
|
|
|
|
|
|
|
static inline void dccp_event_ack_sent(struct sock *sk)
|
|
|
|
{
|
|
|
|
inet_csk_clear_xmit_timer(sk, ICSK_TIME_DACK);
|
|
|
|
}
|
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
static void dccp_skb_entail(struct sock *sk, struct sk_buff *skb)
|
2005-10-29 20:20:59 -04:00
|
|
|
{
|
|
|
|
skb_set_owner_w(skb, sk);
|
|
|
|
WARN_ON(sk->sk_send_head);
|
|
|
|
sk->sk_send_head = skb;
|
|
|
|
}
|
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
/*
|
|
|
|
* All SKB's seen here are completely headerless. It is our
|
|
|
|
* job to build the DCCP header, and pass the packet down to
|
|
|
|
* IP so it can do the same plus pass the packet off to the
|
|
|
|
* device.
|
|
|
|
*/
|
2005-10-29 20:20:59 -04:00
|
|
|
static int dccp_transmit_skb(struct sock *sk, struct sk_buff *skb)
|
2005-08-09 23:14:34 -04:00
|
|
|
{
|
|
|
|
if (likely(skb != NULL)) {
|
|
|
|
const struct inet_sock *inet = inet_sk(sk);
|
2005-12-14 02:16:16 -05:00
|
|
|
const struct inet_connection_sock *icsk = inet_csk(sk);
|
2005-08-09 23:14:34 -04:00
|
|
|
struct dccp_sock *dp = dccp_sk(sk);
|
|
|
|
struct dccp_skb_cb *dcb = DCCP_SKB_CB(skb);
|
|
|
|
struct dccp_hdr *dh;
|
|
|
|
/* XXX For now we're using only 48 bits sequence numbers */
|
2006-03-21 01:31:09 -05:00
|
|
|
const u32 dccp_header_size = sizeof(*dh) +
|
2005-08-09 23:14:34 -04:00
|
|
|
sizeof(struct dccp_hdr_ext) +
|
2005-08-13 19:34:54 -04:00
|
|
|
dccp_packet_hdr_len(dcb->dccpd_type);
|
2005-08-09 23:14:34 -04:00
|
|
|
int err, set_ack = 1;
|
|
|
|
u64 ackno = dp->dccps_gsr;
|
dccp: Bug-Fix - AWL was never updated
The AWL lower Ack validity window advances in proportion to GSS, the greatest
sequence number sent. Updating AWL other than at connection setup (in the
DCCP-Request sent by dccp_v{4,6}_connect()) was missing in the DCCP code.
This bug lead to syslog messages such as
"kernel: dccp_check_seqno: DCCP: Step 6 failed for DATAACK packet, [...]
P.ackno exists or LAWL(82947089) <= P.ackno(82948208)
<= S.AWH(82948728), sending SYNC..."
The difference between AWL/AWH here is 1639 packets, while the expected value
(the Sequence Window) would have been 100 (the default). A closer look showed
that LAWL = AWL = 82947089 equalled the ISS on the Response.
The patch now updates AWL with each increase of GSS.
Further changes:
----------------
The patch also enforces more stringent checks on the ISS sequence number:
* AWL is initialised to ISS at connection setup and remains at this value;
* AWH is then always set to GSS (via dccp_update_gss());
* so on the first Request: AWL = AWH = ISS,
and on the n-th Request: AWL = ISS, AWH = ISS + n.
As a consequence, only Response packets that refer to Requests sent by this
host will pass, all others are discarded. This is the intention and in effect
implements the initial adjustments for AWL as specified in RFC 4340, 7.5.1.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
2008-07-26 06:59:10 -04:00
|
|
|
/*
|
|
|
|
* Increment GSS here already in case the option code needs it.
|
|
|
|
* Update GSS for real only if option processing below succeeds.
|
|
|
|
*/
|
|
|
|
dcb->dccpd_seq = ADD48(dp->dccps_gss, 1);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
switch (dcb->dccpd_type) {
|
|
|
|
case DCCP_PKT_DATA:
|
|
|
|
set_ack = 0;
|
2005-10-29 20:20:59 -04:00
|
|
|
/* fall through */
|
|
|
|
case DCCP_PKT_DATAACK:
|
2007-09-26 10:30:02 -04:00
|
|
|
case DCCP_PKT_RESET:
|
2005-08-09 23:14:34 -04:00
|
|
|
break;
|
2005-10-29 20:20:59 -04: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-20 20:43:56 -05:00
|
|
|
case DCCP_PKT_REQUEST:
|
|
|
|
set_ack = 0;
|
dccp: Bug-Fix - AWL was never updated
The AWL lower Ack validity window advances in proportion to GSS, the greatest
sequence number sent. Updating AWL other than at connection setup (in the
DCCP-Request sent by dccp_v{4,6}_connect()) was missing in the DCCP code.
This bug lead to syslog messages such as
"kernel: dccp_check_seqno: DCCP: Step 6 failed for DATAACK packet, [...]
P.ackno exists or LAWL(82947089) <= P.ackno(82948208)
<= S.AWH(82948728), sending SYNC..."
The difference between AWL/AWH here is 1639 packets, while the expected value
(the Sequence Window) would have been 100 (the default). A closer look showed
that LAWL = AWL = 82947089 equalled the ISS on the Response.
The patch now updates AWL with each increase of GSS.
Further changes:
----------------
The patch also enforces more stringent checks on the ISS sequence number:
* AWL is initialised to ISS at connection setup and remains at this value;
* AWH is then always set to GSS (via dccp_update_gss());
* so on the first Request: AWL = AWH = ISS,
and on the n-th Request: AWL = ISS, AWH = ISS + n.
As a consequence, only Response packets that refer to Requests sent by this
host will pass, all others are discarded. This is the intention and in effect
implements the initial adjustments for AWL as specified in RFC 4340, 7.5.1.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
2008-07-26 06:59:10 -04:00
|
|
|
/* Use ISS on the first (non-retransmitted) Request. */
|
|
|
|
if (icsk->icsk_retransmits == 0)
|
|
|
|
dcb->dccpd_seq = dp->dccps_iss;
|
[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-20 20:43:56 -05:00
|
|
|
/* fall through */
|
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
case DCCP_PKT_SYNC:
|
|
|
|
case DCCP_PKT_SYNCACK:
|
2007-09-26 01:42:27 -04:00
|
|
|
ackno = dcb->dccpd_ack_seq;
|
2005-10-29 20:20:59 -04:00
|
|
|
/* fall through */
|
|
|
|
default:
|
|
|
|
/*
|
2007-09-26 10:30:02 -04:00
|
|
|
* Set owner/destructor: some skbs are allocated via
|
|
|
|
* alloc_skb (e.g. when retransmission may happen).
|
|
|
|
* Only Data, DataAck, and Reset packets should come
|
|
|
|
* through here with skb->sk set.
|
2005-10-29 20:20:59 -04:00
|
|
|
*/
|
|
|
|
WARN_ON(skb->sk);
|
|
|
|
skb_set_owner_w(skb, sk);
|
2005-08-09 23:14:34 -04:00
|
|
|
break;
|
|
|
|
}
|
2005-08-21 04:40:16 -04:00
|
|
|
|
2006-03-21 01:32:06 -05:00
|
|
|
if (dccp_insert_options(sk, skb)) {
|
|
|
|
kfree_skb(skb);
|
|
|
|
return -EPROTO;
|
|
|
|
}
|
2007-02-09 09:24:38 -05:00
|
|
|
|
2005-10-14 02:38:49 -04:00
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
/* Build DCCP header and checksum it. */
|
2006-11-10 08:22:32 -05:00
|
|
|
dh = dccp_zeroed_hdr(skb, dccp_header_size);
|
2005-08-09 23:14:34 -04:00
|
|
|
dh->dccph_type = dcb->dccpd_type;
|
|
|
|
dh->dccph_sport = inet->sport;
|
|
|
|
dh->dccph_dport = inet->dport;
|
|
|
|
dh->dccph_doff = (dccp_header_size + dcb->dccpd_opt_len) / 4;
|
|
|
|
dh->dccph_ccval = dcb->dccpd_ccval;
|
2006-11-10 14:43:06 -05:00
|
|
|
dh->dccph_cscov = dp->dccps_pcslen;
|
2005-08-09 23:14:34 -04:00
|
|
|
/* XXX For now we're using only 48 bits sequence numbers */
|
|
|
|
dh->dccph_x = 1;
|
|
|
|
|
dccp: Bug-Fix - AWL was never updated
The AWL lower Ack validity window advances in proportion to GSS, the greatest
sequence number sent. Updating AWL other than at connection setup (in the
DCCP-Request sent by dccp_v{4,6}_connect()) was missing in the DCCP code.
This bug lead to syslog messages such as
"kernel: dccp_check_seqno: DCCP: Step 6 failed for DATAACK packet, [...]
P.ackno exists or LAWL(82947089) <= P.ackno(82948208)
<= S.AWH(82948728), sending SYNC..."
The difference between AWL/AWH here is 1639 packets, while the expected value
(the Sequence Window) would have been 100 (the default). A closer look showed
that LAWL = AWL = 82947089 equalled the ISS on the Response.
The patch now updates AWL with each increase of GSS.
Further changes:
----------------
The patch also enforces more stringent checks on the ISS sequence number:
* AWL is initialised to ISS at connection setup and remains at this value;
* AWH is then always set to GSS (via dccp_update_gss());
* so on the first Request: AWL = AWH = ISS,
and on the n-th Request: AWL = ISS, AWH = ISS + n.
As a consequence, only Response packets that refer to Requests sent by this
host will pass, all others are discarded. This is the intention and in effect
implements the initial adjustments for AWL as specified in RFC 4340, 7.5.1.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
2008-07-26 06:59:10 -04:00
|
|
|
dccp_update_gss(sk, dcb->dccpd_seq);
|
2005-08-09 23:14:34 -04:00
|
|
|
dccp_hdr_set_seq(dh, dp->dccps_gss);
|
|
|
|
if (set_ack)
|
|
|
|
dccp_hdr_set_ack(dccp_hdr_ack_bits(skb), ackno);
|
|
|
|
|
|
|
|
switch (dcb->dccpd_type) {
|
|
|
|
case DCCP_PKT_REQUEST:
|
2005-08-13 19:34:54 -04:00
|
|
|
dccp_hdr_request(skb)->dccph_req_service =
|
2005-09-16 19:58:40 -04:00
|
|
|
dp->dccps_service;
|
dccp: Bug-Fix - AWL was never updated
The AWL lower Ack validity window advances in proportion to GSS, the greatest
sequence number sent. Updating AWL other than at connection setup (in the
DCCP-Request sent by dccp_v{4,6}_connect()) was missing in the DCCP code.
This bug lead to syslog messages such as
"kernel: dccp_check_seqno: DCCP: Step 6 failed for DATAACK packet, [...]
P.ackno exists or LAWL(82947089) <= P.ackno(82948208)
<= S.AWH(82948728), sending SYNC..."
The difference between AWL/AWH here is 1639 packets, while the expected value
(the Sequence Window) would have been 100 (the default). A closer look showed
that LAWL = AWL = 82947089 equalled the ISS on the Response.
The patch now updates AWL with each increase of GSS.
Further changes:
----------------
The patch also enforces more stringent checks on the ISS sequence number:
* AWL is initialised to ISS at connection setup and remains at this value;
* AWH is then always set to GSS (via dccp_update_gss());
* so on the first Request: AWL = AWH = ISS,
and on the n-th Request: AWL = ISS, AWH = ISS + n.
As a consequence, only Response packets that refer to Requests sent by this
host will pass, all others are discarded. This is the intention and in effect
implements the initial adjustments for AWL as specified in RFC 4340, 7.5.1.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Acked-by: Ian McDonald <ian.mcdonald@jandi.co.nz>
2008-07-26 06:59:10 -04:00
|
|
|
/*
|
|
|
|
* Limit Ack window to ISS <= P.ackno <= GSS, so that
|
|
|
|
* only Responses to Requests we sent are considered.
|
|
|
|
*/
|
|
|
|
dp->dccps_awl = dp->dccps_iss;
|
2005-08-09 23:14:34 -04:00
|
|
|
break;
|
|
|
|
case DCCP_PKT_RESET:
|
2005-08-13 19:34:54 -04:00
|
|
|
dccp_hdr_reset(skb)->dccph_reset_code =
|
|
|
|
dcb->dccpd_reset_code;
|
2005-08-09 23:14:34 -04:00
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
2006-11-10 14:43:06 -05:00
|
|
|
icsk->icsk_af_ops->send_check(sk, 0, skb);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2005-08-24 00:50:06 -04:00
|
|
|
if (set_ack)
|
2005-08-09 23:14:34 -04:00
|
|
|
dccp_event_ack_sent(sk);
|
|
|
|
|
|
|
|
DCCP_INC_STATS(DCCP_MIB_OUTSEGS);
|
|
|
|
|
2007-01-26 04:04:55 -05:00
|
|
|
err = icsk->icsk_af_ops->queue_xmit(skb, 0);
|
2006-11-14 08:21:36 -05:00
|
|
|
return net_xmit_eval(err);
|
2005-08-09 23:14:34 -04:00
|
|
|
}
|
|
|
|
return -ENOBUFS;
|
|
|
|
}
|
|
|
|
|
2007-12-13 20:37:55 -05:00
|
|
|
/**
|
|
|
|
* dccp_determine_ccmps - Find out about CCID-specfic packet-size limits
|
|
|
|
* We only consider the HC-sender CCID for setting the CCMPS (RFC 4340, 14.),
|
|
|
|
* since the RX CCID is restricted to feedback packets (Acks), which are small
|
|
|
|
* in comparison with the data traffic. A value of 0 means "no current CCMPS".
|
|
|
|
*/
|
|
|
|
static u32 dccp_determine_ccmps(const struct dccp_sock *dp)
|
|
|
|
{
|
|
|
|
const struct ccid *tx_ccid = dp->dccps_hc_tx_ccid;
|
|
|
|
|
|
|
|
if (tx_ccid == NULL || tx_ccid->ccid_ops == NULL)
|
|
|
|
return 0;
|
|
|
|
return tx_ccid->ccid_ops->ccid_ccmps;
|
|
|
|
}
|
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
unsigned int dccp_sync_mss(struct sock *sk, u32 pmtu)
|
|
|
|
{
|
2005-12-14 02:26:10 -05:00
|
|
|
struct inet_connection_sock *icsk = inet_csk(sk);
|
2005-08-09 23:14:34 -04:00
|
|
|
struct dccp_sock *dp = dccp_sk(sk);
|
2007-12-13 20:37:55 -05:00
|
|
|
u32 ccmps = dccp_determine_ccmps(dp);
|
2008-09-09 07:27:22 -04:00
|
|
|
int cur_mps = ccmps ? min(pmtu, ccmps) : pmtu;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2007-12-13 20:37:55 -05:00
|
|
|
/* Account for header lengths and IPv4/v6 option overhead */
|
|
|
|
cur_mps -= (icsk->icsk_af_ops->net_header_len + icsk->icsk_ext_hdr_len +
|
|
|
|
sizeof(struct dccp_hdr) + sizeof(struct dccp_hdr_ext));
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
/*
|
2008-09-09 07:27:22 -04:00
|
|
|
* FIXME: this should come from the CCID infrastructure, where, say,
|
|
|
|
* TFRC will say it wants TIMESTAMPS, ELAPSED time, etc, for now lets
|
|
|
|
* put a rough estimate for NDP + TIMESTAMP + TIMESTAMP_ECHO + ELAPSED
|
|
|
|
* TIME + TFRC_OPT_LOSS_EVENT_RATE + TFRC_OPT_RECEIVE_RATE + padding to
|
|
|
|
* make it a multiple of 4
|
2005-08-09 23:14:34 -04:00
|
|
|
*/
|
2008-09-09 07:27:22 -04:00
|
|
|
|
|
|
|
cur_mps -= ((5 + 6 + 10 + 6 + 6 + 6 + 3) / 4) * 4;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
/* And store cached results */
|
2005-12-14 02:26:10 -05:00
|
|
|
icsk->icsk_pmtu_cookie = pmtu;
|
2007-12-13 20:37:55 -05:00
|
|
|
dp->dccps_mss_cache = cur_mps;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2007-12-13 20:37:55 -05:00
|
|
|
return cur_mps;
|
2005-08-09 23:14:34 -04:00
|
|
|
}
|
|
|
|
|
2005-12-14 02:24:16 -05:00
|
|
|
EXPORT_SYMBOL_GPL(dccp_sync_mss);
|
|
|
|
|
2005-08-29 01:15:54 -04:00
|
|
|
void dccp_write_space(struct sock *sk)
|
|
|
|
{
|
|
|
|
read_lock(&sk->sk_callback_lock);
|
|
|
|
|
|
|
|
if (sk->sk_sleep && waitqueue_active(sk->sk_sleep))
|
|
|
|
wake_up_interruptible(sk->sk_sleep);
|
|
|
|
/* Should agree with poll, otherwise some programs break */
|
|
|
|
if (sock_writeable(sk))
|
2007-11-26 07:10:50 -05:00
|
|
|
sk_wake_async(sk, SOCK_WAKE_SPACE, POLL_OUT);
|
2005-08-29 01:15:54 -04:00
|
|
|
|
|
|
|
read_unlock(&sk->sk_callback_lock);
|
|
|
|
}
|
|
|
|
|
2005-08-27 02:06:35 -04:00
|
|
|
/**
|
2008-09-09 07:27:22 -04:00
|
|
|
* dccp_wait_for_ccid - Wait for ccid to tell us we can send a packet
|
2007-10-04 17:38:49 -04:00
|
|
|
* @sk: socket to wait for
|
2008-09-09 07:27:22 -04:00
|
|
|
* @skb: current skb to pass on for waiting
|
|
|
|
* @delay: sleep timeout in milliseconds (> 0)
|
|
|
|
* This function is called by default when the socket is closed, and
|
|
|
|
* when a non-zero linger time is set on the socket. For consistency
|
2005-08-27 02:06:35 -04:00
|
|
|
*/
|
2008-09-09 07:27:22 -04:00
|
|
|
static int dccp_wait_for_ccid(struct sock *sk, struct sk_buff *skb, int delay)
|
2005-08-27 02:06:35 -04:00
|
|
|
{
|
2008-09-09 07:27:22 -04:00
|
|
|
struct dccp_sock *dp = dccp_sk(sk);
|
2005-08-27 02:06:35 -04:00
|
|
|
DEFINE_WAIT(wait);
|
2008-09-09 07:27:22 -04:00
|
|
|
unsigned long jiffdelay;
|
|
|
|
int rc;
|
2007-10-04 17:38:49 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
do {
|
|
|
|
dccp_pr_debug("delayed send by %d msec\n", delay);
|
|
|
|
jiffdelay = msecs_to_jiffies(delay);
|
dccp: Refine the wait-for-ccid mechanism
This extends the existing wait-for-ccid routine so that it may be used with
different types of CCID. It further addresses the problems listed below.
The code looks if the write queue is non-empty and grants the TX CCID up to
`timeout' jiffies to drain the queue. It will instead purge that queue if
* the delay suggested by the CCID exceeds the time budget;
* a socket error occurred while waiting for the CCID;
* there is a signal pending (eg. annoyed user pressed Control-C);
* the CCID does not support delays (we don't know how long it will take).
D e t a i l s [can be removed]
-------------------------------
DCCP's sending mechanism functions a bit like non-blocking I/O: dccp_sendmsg()
will enqueue up to net.dccp.default.tx_qlen packets (default=5), without waiting
for them to be released to the network.
Rate-based CCIDs, such as CCID3/4, can impose sending delays of up to maximally
64 seconds (t_mbi in RFC 3448). Hence the write queue may still contain packets
when the application closes. Since the write queue is congestion-controlled by
the CCID, draining the queue is also under control of the CCID.
There are several problems that needed to be addressed:
1) The queue-drain mechanism only works with rate-based CCIDs. If CCID2 for
example has a full TX queue and becomes network-limited just as the
application wants to close, then waiting for CCID2 to become unblocked could
lead to an indefinite delay (i.e., application "hangs").
2) Since each TX CCID in turn uses a feedback mechanism, there may be changes
in its sending policy while the queue is being drained. This can lead to
further delays during which the application will not be able to terminate.
3) The minimum wait time for CCID3/4 can be expected to be the queue length
times the current inter-packet delay. For example if tx_qlen=100 and a delay
of 15 ms is used for each packet, then the application would have to wait
for a minimum of 1.5 seconds before being allowed to exit.
4) There is no way for the user/application to control this behaviour. It would
be good to use the timeout argument of dccp_close() as an upper bound. Then
the maximum time that an application is willing to wait for its CCIDs to can
be set via the SO_LINGER option.
These problems are addressed by giving the CCID a grace period of up to the
`timeout' value.
The wait-for-ccid function is, as before, used when the application
(a) has read all the data in its receive buffer and
(b) if SO_LINGER was set with a non-zero linger time, or
(c) the socket is either in the OPEN (active close) or in the PASSIVE_CLOSEREQ
state (client application closes after receiving CloseReq).
In addition, there is a catch-all case by calling __skb_queue_purge() after
waiting for the CCID. This is necessary since the write queue may still have
data when
(a) the host has been passively-closed,
(b) abnormal termination (unread data, zero linger time),
(c) wait-for-ccid could not finish within the given time limit.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
prepare_to_wait(sk->sk_sleep, &wait, TASK_INTERRUPTIBLE);
|
dccp: Extend CCID packet dequeueing interface
This extends the packet dequeuing interface of dccp_write_xmit() to allow
1. CCIDs to take care of timing when the next packet may be sent;
2. delayed sending (as before, with an inter-packet gap up to 65.535 seconds).
The main purpose is to take CCID2 out of its polling mode (when it is network-
limited, it tries every millisecond to send, without interruption).
The interface can also be used to support other CCIDs.
The mode of operation for (2) is as follows:
* new packet is enqueued via dccp_sendmsg() => dccp_write_xmit(),
* ccid_hc_tx_send_packet() detects that it may not send (e.g. window full),
* it signals this condition via `CCID_PACKET_WILL_DEQUEUE_LATER',
* dccp_write_xmit() returns without further action;
* after some time the wait-condition for CCID becomes true,
* that CCID schedules the tasklet,
* tasklet function calls ccid_hc_tx_send_packet() via dccp_write_xmit(),
* since the wait-condition is now true, ccid_hc_tx_packet() returns "send now",
* packet is sent, and possibly more (since dccp_write_xmit() loops).
Code reuse: the taskled function calls dccp_write_xmit(), the timer function
reduces to a wrapper around the same code.
If the tasklet finds that the socket is locked, it re-schedules the tasklet
function (not the tasklet) after one jiffy.
Changed DCCP_BUG to dccp_pr_debug when transmit_skb returns an error (e.g. when a
local qdisc is used, NET_XMIT_DROP=1 can be returned for many packets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
sk->sk_write_pending++;
|
|
|
|
release_sock(sk);
|
|
|
|
schedule_timeout(jiffdelay);
|
|
|
|
lock_sock(sk);
|
|
|
|
sk->sk_write_pending--;
|
dccp: Extend CCID packet dequeueing interface
This extends the packet dequeuing interface of dccp_write_xmit() to allow
1. CCIDs to take care of timing when the next packet may be sent;
2. delayed sending (as before, with an inter-packet gap up to 65.535 seconds).
The main purpose is to take CCID2 out of its polling mode (when it is network-
limited, it tries every millisecond to send, without interruption).
The interface can also be used to support other CCIDs.
The mode of operation for (2) is as follows:
* new packet is enqueued via dccp_sendmsg() => dccp_write_xmit(),
* ccid_hc_tx_send_packet() detects that it may not send (e.g. window full),
* it signals this condition via `CCID_PACKET_WILL_DEQUEUE_LATER',
* dccp_write_xmit() returns without further action;
* after some time the wait-condition for CCID becomes true,
* that CCID schedules the tasklet,
* tasklet function calls ccid_hc_tx_send_packet() via dccp_write_xmit(),
* since the wait-condition is now true, ccid_hc_tx_packet() returns "send now",
* packet is sent, and possibly more (since dccp_write_xmit() loops).
Code reuse: the taskled function calls dccp_write_xmit(), the timer function
reduces to a wrapper around the same code.
If the tasklet finds that the socket is locked, it re-schedules the tasklet
function (not the tasklet) after one jiffy.
Changed DCCP_BUG to dccp_pr_debug when transmit_skb returns an error (e.g. when a
local qdisc is used, NET_XMIT_DROP=1 can be returned for many packets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
if (sk->sk_err)
|
|
|
|
goto do_error;
|
|
|
|
if (signal_pending(current))
|
|
|
|
goto do_interrupted;
|
dccp: Extend CCID packet dequeueing interface
This extends the packet dequeuing interface of dccp_write_xmit() to allow
1. CCIDs to take care of timing when the next packet may be sent;
2. delayed sending (as before, with an inter-packet gap up to 65.535 seconds).
The main purpose is to take CCID2 out of its polling mode (when it is network-
limited, it tries every millisecond to send, without interruption).
The interface can also be used to support other CCIDs.
The mode of operation for (2) is as follows:
* new packet is enqueued via dccp_sendmsg() => dccp_write_xmit(),
* ccid_hc_tx_send_packet() detects that it may not send (e.g. window full),
* it signals this condition via `CCID_PACKET_WILL_DEQUEUE_LATER',
* dccp_write_xmit() returns without further action;
* after some time the wait-condition for CCID becomes true,
* that CCID schedules the tasklet,
* tasklet function calls ccid_hc_tx_send_packet() via dccp_write_xmit(),
* since the wait-condition is now true, ccid_hc_tx_packet() returns "send now",
* packet is sent, and possibly more (since dccp_write_xmit() loops).
Code reuse: the taskled function calls dccp_write_xmit(), the timer function
reduces to a wrapper around the same code.
If the tasklet finds that the socket is locked, it re-schedules the tasklet
function (not the tasklet) after one jiffy.
Changed DCCP_BUG to dccp_pr_debug when transmit_skb returns an error (e.g. when a
local qdisc is used, NET_XMIT_DROP=1 can be returned for many packets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
rc = ccid_hc_tx_send_packet(dp->dccps_hc_tx_ccid, sk, skb);
|
|
|
|
} while ((delay = rc) > 0);
|
|
|
|
out:
|
|
|
|
finish_wait(sk->sk_sleep, &wait);
|
|
|
|
return rc;
|
|
|
|
|
|
|
|
do_error:
|
|
|
|
rc = -EPIPE;
|
|
|
|
goto out;
|
|
|
|
do_interrupted:
|
|
|
|
rc = -EINTR;
|
|
|
|
goto out;
|
dccp: Extend CCID packet dequeueing interface
This extends the packet dequeuing interface of dccp_write_xmit() to allow
1. CCIDs to take care of timing when the next packet may be sent;
2. delayed sending (as before, with an inter-packet gap up to 65.535 seconds).
The main purpose is to take CCID2 out of its polling mode (when it is network-
limited, it tries every millisecond to send, without interruption).
The interface can also be used to support other CCIDs.
The mode of operation for (2) is as follows:
* new packet is enqueued via dccp_sendmsg() => dccp_write_xmit(),
* ccid_hc_tx_send_packet() detects that it may not send (e.g. window full),
* it signals this condition via `CCID_PACKET_WILL_DEQUEUE_LATER',
* dccp_write_xmit() returns without further action;
* after some time the wait-condition for CCID becomes true,
* that CCID schedules the tasklet,
* tasklet function calls ccid_hc_tx_send_packet() via dccp_write_xmit(),
* since the wait-condition is now true, ccid_hc_tx_packet() returns "send now",
* packet is sent, and possibly more (since dccp_write_xmit() loops).
Code reuse: the taskled function calls dccp_write_xmit(), the timer function
reduces to a wrapper around the same code.
If the tasklet finds that the socket is locked, it re-schedules the tasklet
function (not the tasklet) after one jiffy.
Changed DCCP_BUG to dccp_pr_debug when transmit_skb returns an error (e.g. when a
local qdisc is used, NET_XMIT_DROP=1 can be returned for many packets).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
}
|
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
void dccp_write_xmit(struct sock *sk, int block)
|
dccp: Refine the wait-for-ccid mechanism
This extends the existing wait-for-ccid routine so that it may be used with
different types of CCID. It further addresses the problems listed below.
The code looks if the write queue is non-empty and grants the TX CCID up to
`timeout' jiffies to drain the queue. It will instead purge that queue if
* the delay suggested by the CCID exceeds the time budget;
* a socket error occurred while waiting for the CCID;
* there is a signal pending (eg. annoyed user pressed Control-C);
* the CCID does not support delays (we don't know how long it will take).
D e t a i l s [can be removed]
-------------------------------
DCCP's sending mechanism functions a bit like non-blocking I/O: dccp_sendmsg()
will enqueue up to net.dccp.default.tx_qlen packets (default=5), without waiting
for them to be released to the network.
Rate-based CCIDs, such as CCID3/4, can impose sending delays of up to maximally
64 seconds (t_mbi in RFC 3448). Hence the write queue may still contain packets
when the application closes. Since the write queue is congestion-controlled by
the CCID, draining the queue is also under control of the CCID.
There are several problems that needed to be addressed:
1) The queue-drain mechanism only works with rate-based CCIDs. If CCID2 for
example has a full TX queue and becomes network-limited just as the
application wants to close, then waiting for CCID2 to become unblocked could
lead to an indefinite delay (i.e., application "hangs").
2) Since each TX CCID in turn uses a feedback mechanism, there may be changes
in its sending policy while the queue is being drained. This can lead to
further delays during which the application will not be able to terminate.
3) The minimum wait time for CCID3/4 can be expected to be the queue length
times the current inter-packet delay. For example if tx_qlen=100 and a delay
of 15 ms is used for each packet, then the application would have to wait
for a minimum of 1.5 seconds before being allowed to exit.
4) There is no way for the user/application to control this behaviour. It would
be good to use the timeout argument of dccp_close() as an upper bound. Then
the maximum time that an application is willing to wait for its CCIDs to can
be set via the SO_LINGER option.
These problems are addressed by giving the CCID a grace period of up to the
`timeout' value.
The wait-for-ccid function is, as before, used when the application
(a) has read all the data in its receive buffer and
(b) if SO_LINGER was set with a non-zero linger time, or
(c) the socket is either in the OPEN (active close) or in the PASSIVE_CLOSEREQ
state (client application closes after receiving CloseReq).
In addition, there is a catch-all case by calling __skb_queue_purge() after
waiting for the CCID. This is necessary since the write queue may still have
data when
(a) the host has been passively-closed,
(b) abnormal termination (unread data, zero linger time),
(c) wait-for-ccid could not finish within the given time limit.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
{
|
|
|
|
struct dccp_sock *dp = dccp_sk(sk);
|
|
|
|
struct sk_buff *skb;
|
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
while ((skb = skb_peek(&sk->sk_write_queue))) {
|
|
|
|
int err = ccid_hc_tx_send_packet(dp->dccps_hc_tx_ccid, sk, skb);
|
|
|
|
|
|
|
|
if (err > 0) {
|
|
|
|
if (!block) {
|
|
|
|
sk_reset_timer(sk, &dp->dccps_xmit_timer,
|
|
|
|
msecs_to_jiffies(err)+jiffies);
|
|
|
|
break;
|
|
|
|
} else
|
|
|
|
err = dccp_wait_for_ccid(sk, skb, err);
|
|
|
|
if (err && err != -EINTR)
|
|
|
|
DCCP_BUG("err=%d after dccp_wait_for_ccid", err);
|
dccp: Refine the wait-for-ccid mechanism
This extends the existing wait-for-ccid routine so that it may be used with
different types of CCID. It further addresses the problems listed below.
The code looks if the write queue is non-empty and grants the TX CCID up to
`timeout' jiffies to drain the queue. It will instead purge that queue if
* the delay suggested by the CCID exceeds the time budget;
* a socket error occurred while waiting for the CCID;
* there is a signal pending (eg. annoyed user pressed Control-C);
* the CCID does not support delays (we don't know how long it will take).
D e t a i l s [can be removed]
-------------------------------
DCCP's sending mechanism functions a bit like non-blocking I/O: dccp_sendmsg()
will enqueue up to net.dccp.default.tx_qlen packets (default=5), without waiting
for them to be released to the network.
Rate-based CCIDs, such as CCID3/4, can impose sending delays of up to maximally
64 seconds (t_mbi in RFC 3448). Hence the write queue may still contain packets
when the application closes. Since the write queue is congestion-controlled by
the CCID, draining the queue is also under control of the CCID.
There are several problems that needed to be addressed:
1) The queue-drain mechanism only works with rate-based CCIDs. If CCID2 for
example has a full TX queue and becomes network-limited just as the
application wants to close, then waiting for CCID2 to become unblocked could
lead to an indefinite delay (i.e., application "hangs").
2) Since each TX CCID in turn uses a feedback mechanism, there may be changes
in its sending policy while the queue is being drained. This can lead to
further delays during which the application will not be able to terminate.
3) The minimum wait time for CCID3/4 can be expected to be the queue length
times the current inter-packet delay. For example if tx_qlen=100 and a delay
of 15 ms is used for each packet, then the application would have to wait
for a minimum of 1.5 seconds before being allowed to exit.
4) There is no way for the user/application to control this behaviour. It would
be good to use the timeout argument of dccp_close() as an upper bound. Then
the maximum time that an application is willing to wait for its CCIDs to can
be set via the SO_LINGER option.
These problems are addressed by giving the CCID a grace period of up to the
`timeout' value.
The wait-for-ccid function is, as before, used when the application
(a) has read all the data in its receive buffer and
(b) if SO_LINGER was set with a non-zero linger time, or
(c) the socket is either in the OPEN (active close) or in the PASSIVE_CLOSEREQ
state (client application closes after receiving CloseReq).
In addition, there is a catch-all case by calling __skb_queue_purge() after
waiting for the CCID. This is necessary since the write queue may still have
data when
(a) the host has been passively-closed,
(b) abnormal termination (unread data, zero linger time),
(c) wait-for-ccid could not finish within the given time limit.
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
2008-09-04 01:30:19 -04:00
|
|
|
}
|
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
skb_dequeue(&sk->sk_write_queue);
|
|
|
|
if (err == 0) {
|
|
|
|
struct dccp_skb_cb *dcb = DCCP_SKB_CB(skb);
|
|
|
|
const int len = skb->len;
|
2006-08-26 22:16:45 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
if (sk->sk_state == DCCP_PARTOPEN) {
|
|
|
|
/* See 8.1.5. Handshake Completion */
|
|
|
|
inet_csk_schedule_ack(sk);
|
|
|
|
inet_csk_reset_xmit_timer(sk, ICSK_TIME_DACK,
|
|
|
|
inet_csk(sk)->icsk_rto,
|
|
|
|
DCCP_RTO_MAX);
|
|
|
|
dcb->dccpd_type = DCCP_PKT_DATAACK;
|
|
|
|
} else if (dccp_ack_pending(sk))
|
|
|
|
dcb->dccpd_type = DCCP_PKT_DATAACK;
|
|
|
|
else
|
|
|
|
dcb->dccpd_type = DCCP_PKT_DATA;
|
|
|
|
|
|
|
|
err = dccp_transmit_skb(sk, skb);
|
|
|
|
ccid_hc_tx_packet_sent(dp->dccps_hc_tx_ccid, sk, 0, len);
|
|
|
|
if (err)
|
|
|
|
DCCP_BUG("err=%d after ccid_hc_tx_packet_sent",
|
|
|
|
err);
|
|
|
|
} else {
|
|
|
|
dccp_pr_debug("packet discarded due to err=%d\n", err);
|
|
|
|
kfree_skb(skb);
|
2006-12-09 21:05:12 -05:00
|
|
|
}
|
2006-08-26 22:16:45 -04:00
|
|
|
}
|
2005-08-09 23:30:56 -04:00
|
|
|
}
|
|
|
|
|
2008-07-26 06:59:09 -04:00
|
|
|
/**
|
|
|
|
* dccp_retransmit_skb - Retransmit Request, Close, or CloseReq packets
|
|
|
|
* There are only four retransmittable packet types in DCCP:
|
|
|
|
* - Request in client-REQUEST state (sec. 8.1.1),
|
|
|
|
* - CloseReq in server-CLOSEREQ state (sec. 8.3),
|
|
|
|
* - Close in node-CLOSING state (sec. 8.3),
|
|
|
|
* - Acks in client-PARTOPEN state (sec. 8.1.5, handled by dccp_delack_timer()).
|
|
|
|
* This function expects sk->sk_send_head to contain the original skb.
|
|
|
|
*/
|
|
|
|
int dccp_retransmit_skb(struct sock *sk)
|
2005-08-09 23:14:34 -04:00
|
|
|
{
|
2008-07-26 06:59:09 -04:00
|
|
|
WARN_ON(sk->sk_send_head == NULL);
|
|
|
|
|
2005-12-14 02:16:16 -05:00
|
|
|
if (inet_csk(sk)->icsk_af_ops->rebuild_header(sk) != 0)
|
2005-08-09 23:14:34 -04:00
|
|
|
return -EHOSTUNREACH; /* Routing failure or similar. */
|
|
|
|
|
2008-07-26 06:59:09 -04:00
|
|
|
/* this count is used to distinguish original and retransmitted skb */
|
|
|
|
inet_csk(sk)->icsk_retransmits++;
|
|
|
|
|
|
|
|
return dccp_transmit_skb(sk, skb_clone(sk->sk_send_head, GFP_ATOMIC));
|
2005-08-09 23:14:34 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
struct sk_buff *dccp_make_response(struct sock *sk, struct dst_entry *dst,
|
|
|
|
struct request_sock *req)
|
|
|
|
{
|
|
|
|
struct dccp_hdr *dh;
|
2005-09-16 19:58:40 -04:00
|
|
|
struct dccp_request_sock *dreq;
|
2006-03-21 01:31:09 -05:00
|
|
|
const u32 dccp_header_size = sizeof(struct dccp_hdr) +
|
2005-08-09 23:14:34 -04:00
|
|
|
sizeof(struct dccp_hdr_ext) +
|
|
|
|
sizeof(struct dccp_hdr_response);
|
2006-03-21 01:31:09 -05:00
|
|
|
struct sk_buff *skb = sock_wmalloc(sk, sk->sk_prot->max_header, 1,
|
2005-08-09 23:14:34 -04:00
|
|
|
GFP_ATOMIC);
|
|
|
|
if (skb == NULL)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
/* Reserve space for headers. */
|
2006-03-21 01:31:09 -05:00
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
skb->dst = dst_clone(dst);
|
|
|
|
|
2005-09-16 19:58:40 -04:00
|
|
|
dreq = dccp_rsk(req);
|
2006-11-13 10:12:07 -05:00
|
|
|
if (inet_rsk(req)->acked) /* increase ISS upon retransmission */
|
|
|
|
dccp_inc_seqno(&dreq->dreq_iss);
|
2005-08-09 23:14:34 -04:00
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = DCCP_PKT_RESPONSE;
|
2005-09-16 19:58:40 -04:00
|
|
|
DCCP_SKB_CB(skb)->dccpd_seq = dreq->dreq_iss;
|
2006-03-21 01:32:06 -05:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
if (dccp_insert_options_rsk(dreq, skb)) {
|
|
|
|
kfree_skb(skb);
|
|
|
|
return NULL;
|
|
|
|
}
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2006-11-14 09:57:34 -05:00
|
|
|
/* Build and checksum header */
|
2006-11-10 08:22:32 -05:00
|
|
|
dh = dccp_zeroed_hdr(skb, dccp_header_size);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
dh->dccph_sport = inet_sk(sk)->sport;
|
|
|
|
dh->dccph_dport = inet_rsk(req)->rmt_port;
|
2005-08-13 19:34:54 -04:00
|
|
|
dh->dccph_doff = (dccp_header_size +
|
|
|
|
DCCP_SKB_CB(skb)->dccpd_opt_len) / 4;
|
2005-08-09 23:14:34 -04:00
|
|
|
dh->dccph_type = DCCP_PKT_RESPONSE;
|
|
|
|
dh->dccph_x = 1;
|
2005-09-16 19:58:40 -04:00
|
|
|
dccp_hdr_set_seq(dh, dreq->dreq_iss);
|
|
|
|
dccp_hdr_set_ack(dccp_hdr_ack_bits(skb), dreq->dreq_isr);
|
|
|
|
dccp_hdr_response(skb)->dccph_resp_service = dreq->dreq_service;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2006-11-10 14:43:06 -05:00
|
|
|
dccp_csum_outgoing(skb);
|
|
|
|
|
2006-11-13 10:12:07 -05:00
|
|
|
/* We use `acked' to remember that a Response was already sent. */
|
|
|
|
inet_rsk(req)->acked = 1;
|
2005-08-09 23:14:34 -04:00
|
|
|
DCCP_INC_STATS(DCCP_MIB_OUTSEGS);
|
|
|
|
return skb;
|
|
|
|
}
|
|
|
|
|
2005-12-14 02:24:16 -05:00
|
|
|
EXPORT_SYMBOL_GPL(dccp_make_response);
|
|
|
|
|
[DCCP]: Factor out common code for generating Resets
This factors code common to dccp_v{4,6}_ctl_send_reset into a separate function,
and adds support for filling in the Data 1 ... Data 3 fields from RFC 4340, 5.6.
It is useful to have this separate, since the following Reset codes will always
be generated from the control socket rather than via dccp_send_reset:
* Code 3, "No Connection", cf. 8.3.1;
* Code 4, "Packet Error" (identification for Data 1 added);
* Code 5, "Option Error" (identification for Data 1..3 added, will be used later);
* Code 6, "Mandatory Error" (same as Option Error);
* Code 7, "Connection Refused" (what on Earth is the difference to "No Connection"?);
* Code 8, "Bad Service Code";
* Code 9, "Too Busy";
* Code 10, "Bad Init Cookie" (not used).
Code 0 is not recommended by the RFC, the following codes would be used in
dccp_send_reset() instead, since they all relate to an established DCCP connection:
* Code 1, "Closed";
* Code 2, "Aborted";
* Code 11, "Aggression Penalty" (12.3).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
2007-09-26 13:35:19 -04:00
|
|
|
/* answer offending packet in @rcv_skb with Reset from control socket @ctl */
|
2008-04-03 17:20:52 -04:00
|
|
|
struct sk_buff *dccp_ctl_make_reset(struct sock *sk, struct sk_buff *rcv_skb)
|
[DCCP]: Factor out common code for generating Resets
This factors code common to dccp_v{4,6}_ctl_send_reset into a separate function,
and adds support for filling in the Data 1 ... Data 3 fields from RFC 4340, 5.6.
It is useful to have this separate, since the following Reset codes will always
be generated from the control socket rather than via dccp_send_reset:
* Code 3, "No Connection", cf. 8.3.1;
* Code 4, "Packet Error" (identification for Data 1 added);
* Code 5, "Option Error" (identification for Data 1..3 added, will be used later);
* Code 6, "Mandatory Error" (same as Option Error);
* Code 7, "Connection Refused" (what on Earth is the difference to "No Connection"?);
* Code 8, "Bad Service Code";
* Code 9, "Too Busy";
* Code 10, "Bad Init Cookie" (not used).
Code 0 is not recommended by the RFC, the following codes would be used in
dccp_send_reset() instead, since they all relate to an established DCCP connection:
* Code 1, "Closed";
* Code 2, "Aborted";
* Code 11, "Aggression Penalty" (12.3).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
2007-09-26 13:35:19 -04:00
|
|
|
{
|
|
|
|
struct dccp_hdr *rxdh = dccp_hdr(rcv_skb), *dh;
|
|
|
|
struct dccp_skb_cb *dcb = DCCP_SKB_CB(rcv_skb);
|
|
|
|
const u32 dccp_hdr_reset_len = sizeof(struct dccp_hdr) +
|
|
|
|
sizeof(struct dccp_hdr_ext) +
|
|
|
|
sizeof(struct dccp_hdr_reset);
|
|
|
|
struct dccp_hdr_reset *dhr;
|
|
|
|
struct sk_buff *skb;
|
|
|
|
|
2008-04-03 17:20:52 -04:00
|
|
|
skb = alloc_skb(sk->sk_prot->max_header, GFP_ATOMIC);
|
[DCCP]: Factor out common code for generating Resets
This factors code common to dccp_v{4,6}_ctl_send_reset into a separate function,
and adds support for filling in the Data 1 ... Data 3 fields from RFC 4340, 5.6.
It is useful to have this separate, since the following Reset codes will always
be generated from the control socket rather than via dccp_send_reset:
* Code 3, "No Connection", cf. 8.3.1;
* Code 4, "Packet Error" (identification for Data 1 added);
* Code 5, "Option Error" (identification for Data 1..3 added, will be used later);
* Code 6, "Mandatory Error" (same as Option Error);
* Code 7, "Connection Refused" (what on Earth is the difference to "No Connection"?);
* Code 8, "Bad Service Code";
* Code 9, "Too Busy";
* Code 10, "Bad Init Cookie" (not used).
Code 0 is not recommended by the RFC, the following codes would be used in
dccp_send_reset() instead, since they all relate to an established DCCP connection:
* Code 1, "Closed";
* Code 2, "Aborted";
* Code 11, "Aggression Penalty" (12.3).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
2007-09-26 13:35:19 -04:00
|
|
|
if (skb == NULL)
|
|
|
|
return NULL;
|
|
|
|
|
2008-04-03 17:20:52 -04:00
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
[DCCP]: Factor out common code for generating Resets
This factors code common to dccp_v{4,6}_ctl_send_reset into a separate function,
and adds support for filling in the Data 1 ... Data 3 fields from RFC 4340, 5.6.
It is useful to have this separate, since the following Reset codes will always
be generated from the control socket rather than via dccp_send_reset:
* Code 3, "No Connection", cf. 8.3.1;
* Code 4, "Packet Error" (identification for Data 1 added);
* Code 5, "Option Error" (identification for Data 1..3 added, will be used later);
* Code 6, "Mandatory Error" (same as Option Error);
* Code 7, "Connection Refused" (what on Earth is the difference to "No Connection"?);
* Code 8, "Bad Service Code";
* Code 9, "Too Busy";
* Code 10, "Bad Init Cookie" (not used).
Code 0 is not recommended by the RFC, the following codes would be used in
dccp_send_reset() instead, since they all relate to an established DCCP connection:
* Code 1, "Closed";
* Code 2, "Aborted";
* Code 11, "Aggression Penalty" (12.3).
Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk>
Signed-off-by: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
2007-09-26 13:35:19 -04:00
|
|
|
|
|
|
|
/* Swap the send and the receive. */
|
|
|
|
dh = dccp_zeroed_hdr(skb, dccp_hdr_reset_len);
|
|
|
|
dh->dccph_type = DCCP_PKT_RESET;
|
|
|
|
dh->dccph_sport = rxdh->dccph_dport;
|
|
|
|
dh->dccph_dport = rxdh->dccph_sport;
|
|
|
|
dh->dccph_doff = dccp_hdr_reset_len / 4;
|
|
|
|
dh->dccph_x = 1;
|
|
|
|
|
|
|
|
dhr = dccp_hdr_reset(skb);
|
|
|
|
dhr->dccph_reset_code = dcb->dccpd_reset_code;
|
|
|
|
|
|
|
|
switch (dcb->dccpd_reset_code) {
|
|
|
|
case DCCP_RESET_CODE_PACKET_ERROR:
|
|
|
|
dhr->dccph_reset_data[0] = rxdh->dccph_type;
|
|
|
|
break;
|
|
|
|
case DCCP_RESET_CODE_OPTION_ERROR: /* fall through */
|
|
|
|
case DCCP_RESET_CODE_MANDATORY_ERROR:
|
|
|
|
memcpy(dhr->dccph_reset_data, dcb->dccpd_reset_data, 3);
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
/*
|
|
|
|
* From RFC 4340, 8.3.1:
|
|
|
|
* If P.ackno exists, set R.seqno := P.ackno + 1.
|
|
|
|
* Else set R.seqno := 0.
|
|
|
|
*/
|
|
|
|
if (dcb->dccpd_ack_seq != DCCP_PKT_WITHOUT_ACK_SEQ)
|
|
|
|
dccp_hdr_set_seq(dh, ADD48(dcb->dccpd_ack_seq, 1));
|
|
|
|
dccp_hdr_set_ack(dccp_hdr_ack_bits(skb), dcb->dccpd_seq);
|
|
|
|
|
|
|
|
dccp_csum_outgoing(skb);
|
|
|
|
return skb;
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL_GPL(dccp_ctl_make_reset);
|
|
|
|
|
2007-09-26 10:30:02 -04:00
|
|
|
/* send Reset on established socket, to close or abort the connection */
|
2006-03-20 22:25:24 -05:00
|
|
|
int dccp_send_reset(struct sock *sk, enum dccp_reset_codes code)
|
|
|
|
{
|
2007-09-26 10:30:02 -04:00
|
|
|
struct sk_buff *skb;
|
2006-03-20 22:25:24 -05:00
|
|
|
/*
|
|
|
|
* FIXME: what if rebuild_header fails?
|
|
|
|
* Should we be doing a rebuild_header here?
|
|
|
|
*/
|
2007-11-28 03:35:08 -05:00
|
|
|
int err = inet_csk(sk)->icsk_af_ops->rebuild_header(sk);
|
2006-03-20 22:25:24 -05:00
|
|
|
|
2007-09-26 10:30:02 -04:00
|
|
|
if (err != 0)
|
|
|
|
return err;
|
|
|
|
|
|
|
|
skb = sock_wmalloc(sk, sk->sk_prot->max_header, 1, GFP_ATOMIC);
|
|
|
|
if (skb == NULL)
|
|
|
|
return -ENOBUFS;
|
|
|
|
|
|
|
|
/* Reserve space for headers and prepare control bits. */
|
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = DCCP_PKT_RESET;
|
|
|
|
DCCP_SKB_CB(skb)->dccpd_reset_code = code;
|
2006-03-20 22:25:24 -05:00
|
|
|
|
2007-09-26 10:30:02 -04:00
|
|
|
return dccp_transmit_skb(sk, skb);
|
2006-03-20 22:25:24 -05:00
|
|
|
}
|
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
/*
|
|
|
|
* Do all connect socket setups that can be done AF independent.
|
|
|
|
*/
|
2008-09-09 07:27:22 -04:00
|
|
|
static inline void dccp_connect_init(struct sock *sk)
|
2005-08-09 23:14:34 -04:00
|
|
|
{
|
2005-12-14 02:24:16 -05:00
|
|
|
struct dccp_sock *dp = dccp_sk(sk);
|
2005-08-09 23:14:34 -04:00
|
|
|
struct dst_entry *dst = __sk_dst_get(sk);
|
|
|
|
struct inet_connection_sock *icsk = inet_csk(sk);
|
|
|
|
|
|
|
|
sk->sk_err = 0;
|
|
|
|
sock_reset_flag(sk, SOCK_DONE);
|
2007-02-09 09:24:38 -05:00
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
dccp_sync_mss(sk, dst_mtu(dst));
|
|
|
|
|
2008-09-04 01:30:19 -04:00
|
|
|
/* Initialise GAR as per 8.5; AWL/AWH are set in dccp_transmit_skb() */
|
|
|
|
dp->dccps_gar = dp->dccps_iss;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
icsk->icsk_retransmits = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int dccp_connect(struct sock *sk)
|
|
|
|
{
|
|
|
|
struct sk_buff *skb;
|
|
|
|
struct inet_connection_sock *icsk = inet_csk(sk);
|
|
|
|
|
|
|
|
dccp_connect_init(sk);
|
|
|
|
|
2006-03-21 01:31:09 -05:00
|
|
|
skb = alloc_skb(sk->sk_prot->max_header, sk->sk_allocation);
|
2005-08-09 23:14:34 -04:00
|
|
|
if (unlikely(skb == NULL))
|
|
|
|
return -ENOBUFS;
|
|
|
|
|
|
|
|
/* Reserve space for headers. */
|
2006-03-21 01:31:09 -05:00
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = DCCP_PKT_REQUEST;
|
|
|
|
|
2008-09-09 07:27:22 -04:00
|
|
|
dccp_skb_entail(sk, skb);
|
|
|
|
dccp_transmit_skb(sk, skb_clone(skb, GFP_KERNEL));
|
2005-08-09 23:14:34 -04:00
|
|
|
DCCP_INC_STATS(DCCP_MIB_ACTIVEOPENS);
|
|
|
|
|
|
|
|
/* Timer for repeating the REQUEST until an answer. */
|
2005-08-09 23:30:56 -04:00
|
|
|
inet_csk_reset_xmit_timer(sk, ICSK_TIME_RETRANS,
|
|
|
|
icsk->icsk_rto, DCCP_RTO_MAX);
|
2005-08-09 23:14:34 -04:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2005-12-14 02:24:16 -05:00
|
|
|
EXPORT_SYMBOL_GPL(dccp_connect);
|
|
|
|
|
2005-08-09 23:14:34 -04:00
|
|
|
void dccp_send_ack(struct sock *sk)
|
|
|
|
{
|
|
|
|
/* If we have been reset, we may not send again. */
|
|
|
|
if (sk->sk_state != DCCP_CLOSED) {
|
2006-03-21 01:31:09 -05:00
|
|
|
struct sk_buff *skb = alloc_skb(sk->sk_prot->max_header,
|
|
|
|
GFP_ATOMIC);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
if (skb == NULL) {
|
|
|
|
inet_csk_schedule_ack(sk);
|
|
|
|
inet_csk(sk)->icsk_ack.ato = TCP_ATO_MIN;
|
2005-08-13 19:34:54 -04:00
|
|
|
inet_csk_reset_xmit_timer(sk, ICSK_TIME_DACK,
|
|
|
|
TCP_DELACK_MAX,
|
|
|
|
DCCP_RTO_MAX);
|
2005-08-09 23:14:34 -04:00
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Reserve space for headers */
|
2006-03-21 01:31:09 -05:00
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
2005-08-09 23:14:34 -04:00
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = DCCP_PKT_ACK;
|
|
|
|
dccp_transmit_skb(sk, skb);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
EXPORT_SYMBOL_GPL(dccp_send_ack);
|
|
|
|
|
2008-06-11 06:19:09 -04:00
|
|
|
#if 0
|
2007-09-26 10:26:04 -04:00
|
|
|
/* FIXME: Is this still necessary (11.3) - currently nowhere used by DCCP. */
|
2005-08-09 23:14:34 -04:00
|
|
|
void dccp_send_delayed_ack(struct sock *sk)
|
|
|
|
{
|
|
|
|
struct inet_connection_sock *icsk = inet_csk(sk);
|
|
|
|
/*
|
|
|
|
* FIXME: tune this timer. elapsed time fixes the skew, so no problem
|
|
|
|
* with using 2s, and active senders also piggyback the ACK into a
|
|
|
|
* DATAACK packet, so this is really for quiescent senders.
|
|
|
|
*/
|
|
|
|
unsigned long timeout = jiffies + 2 * HZ;
|
|
|
|
|
|
|
|
/* Use new timeout only if there wasn't a older one earlier. */
|
|
|
|
if (icsk->icsk_ack.pending & ICSK_ACK_TIMER) {
|
|
|
|
/* If delack timer was blocked or is about to expire,
|
|
|
|
* send ACK now.
|
|
|
|
*
|
|
|
|
* FIXME: check the "about to expire" part
|
|
|
|
*/
|
|
|
|
if (icsk->icsk_ack.blocked) {
|
|
|
|
dccp_send_ack(sk);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!time_before(timeout, icsk->icsk_ack.timeout))
|
|
|
|
timeout = icsk->icsk_ack.timeout;
|
|
|
|
}
|
|
|
|
icsk->icsk_ack.pending |= ICSK_ACK_SCHED | ICSK_ACK_TIMER;
|
|
|
|
icsk->icsk_ack.timeout = timeout;
|
|
|
|
sk_reset_timer(sk, &icsk->icsk_delack_timer, timeout);
|
|
|
|
}
|
2008-06-11 06:19:09 -04:00
|
|
|
#endif
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2007-09-26 01:42:27 -04:00
|
|
|
void dccp_send_sync(struct sock *sk, const u64 ackno,
|
2005-08-17 02:10:59 -04:00
|
|
|
const enum dccp_pkt_type pkt_type)
|
2005-08-09 23:14:34 -04:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* We are not putting this on the write queue, so
|
|
|
|
* dccp_transmit_skb() will set the ownership to this
|
|
|
|
* sock.
|
|
|
|
*/
|
2006-03-21 01:31:09 -05:00
|
|
|
struct sk_buff *skb = alloc_skb(sk->sk_prot->max_header, GFP_ATOMIC);
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2007-09-26 01:42:27 -04:00
|
|
|
if (skb == NULL) {
|
2005-08-09 23:14:34 -04:00
|
|
|
/* FIXME: how to make sure the sync is sent? */
|
2007-09-26 01:42:27 -04:00
|
|
|
DCCP_CRIT("could not send %s", dccp_packet_name(pkt_type));
|
2005-08-09 23:14:34 -04:00
|
|
|
return;
|
2007-09-26 01:42:27 -04:00
|
|
|
}
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
/* Reserve space for headers and prepare control bits. */
|
2006-03-21 01:31:09 -05:00
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
2005-08-17 02:10:59 -04:00
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = pkt_type;
|
2007-09-26 01:42:27 -04:00
|
|
|
DCCP_SKB_CB(skb)->dccpd_ack_seq = ackno;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
dccp_transmit_skb(sk, skb);
|
|
|
|
}
|
|
|
|
|
2006-03-21 00:25:11 -05:00
|
|
|
EXPORT_SYMBOL_GPL(dccp_send_sync);
|
|
|
|
|
2005-08-13 19:34:54 -04:00
|
|
|
/*
|
|
|
|
* Send a DCCP_PKT_CLOSE/CLOSEREQ. The caller locks the socket for us. This
|
|
|
|
* cannot be allowed to fail queueing a DCCP_PKT_CLOSE/CLOSEREQ frame under
|
|
|
|
* any circumstances.
|
2005-08-09 23:14:34 -04:00
|
|
|
*/
|
2005-08-24 00:50:06 -04:00
|
|
|
void dccp_send_close(struct sock *sk, const int active)
|
2005-08-09 23:14:34 -04:00
|
|
|
{
|
|
|
|
struct dccp_sock *dp = dccp_sk(sk);
|
|
|
|
struct sk_buff *skb;
|
2005-10-21 03:20:43 -04:00
|
|
|
const gfp_t prio = active ? GFP_KERNEL : GFP_ATOMIC;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2005-08-24 00:50:06 -04:00
|
|
|
skb = alloc_skb(sk->sk_prot->max_header, prio);
|
|
|
|
if (skb == NULL)
|
|
|
|
return;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
|
|
|
/* Reserve space for headers and prepare control bits. */
|
|
|
|
skb_reserve(skb, sk->sk_prot->max_header);
|
2007-12-13 09:25:01 -05:00
|
|
|
if (dp->dccps_role == DCCP_ROLE_SERVER && !dp->dccps_server_timewait)
|
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = DCCP_PKT_CLOSEREQ;
|
|
|
|
else
|
|
|
|
DCCP_SKB_CB(skb)->dccpd_type = DCCP_PKT_CLOSE;
|
2005-08-09 23:14:34 -04:00
|
|
|
|
2005-08-24 00:50:06 -04:00
|
|
|
if (active) {
|
2008-09-09 07:27:22 -04:00
|
|
|
dccp_write_xmit(sk, 1);
|
|
|
|
dccp_skb_entail(sk, skb);
|
|
|
|
dccp_transmit_skb(sk, skb_clone(skb, prio));
|
2007-12-13 09:02:43 -05:00
|
|
|
/*
|
|
|
|
* Retransmission timer for active-close: RFC 4340, 8.3 requires
|
|
|
|
* to retransmit the Close/CloseReq until the CLOSING/CLOSEREQ
|
|
|
|
* state can be left. The initial timeout is 2 RTTs.
|
|
|
|
* Since RTT measurement is done by the CCIDs, there is no easy
|
|
|
|
* way to get an RTT sample. The fallback RTT from RFC 4340, 3.4
|
|
|
|
* is too low (200ms); we use a high value to avoid unnecessary
|
|
|
|
* retransmissions when the link RTT is > 0.2 seconds.
|
|
|
|
* FIXME: Let main module sample RTTs and use that instead.
|
|
|
|
*/
|
|
|
|
inet_csk_reset_xmit_timer(sk, ICSK_TIME_RETRANS,
|
|
|
|
DCCP_TIMEOUT_INIT, DCCP_RTO_MAX);
|
2008-09-09 07:27:22 -04:00
|
|
|
} else
|
|
|
|
dccp_transmit_skb(sk, skb);
|
2005-08-09 23:14:34 -04:00
|
|
|
}
|