[DCCP] options: Fix handling of ackvecs in DATA packets
I.e. they should be just ignored, but we have to use 'break', not 'continue', as we have to possibly reset the mandatory flag. Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
aa837b5bbd
commit
e5a6de915b
|
@ -148,7 +148,7 @@ int dccp_parse_options(struct sock *sk, struct sk_buff *skb)
|
||||||
case DCCPO_ACK_VECTOR_0:
|
case DCCPO_ACK_VECTOR_0:
|
||||||
case DCCPO_ACK_VECTOR_1:
|
case DCCPO_ACK_VECTOR_1:
|
||||||
if (pkt_type == DCCP_PKT_DATA)
|
if (pkt_type == DCCP_PKT_DATA)
|
||||||
continue;
|
break;
|
||||||
|
|
||||||
if (dp->dccps_options.dccpo_send_ack_vector &&
|
if (dp->dccps_options.dccpo_send_ack_vector &&
|
||||||
dccp_ackvec_parse(sk, skb, opt, value, len))
|
dccp_ackvec_parse(sk, skb, opt, value, len))
|
||||||
|
|
Loading…
Reference in a new issue