: One more exemption from full sequence number checks
PATCH 2/3 : One more exemption from full sequence number checks
[DCCP]: One more exemption from full sequence number checks
This fixes the following problem: client connects to peer which has no DCCP enabled or loaded; ICMP error messages ("Protocol Unavailable") can be seen on the wire, but the application hangs. Reason: ICMP packets don't get through to dccp_v4_err.
When reporting errors, a sequence number check is made for the DCCP packet that had caused an ICMP error to arrive.
Such checks can not be made if the socket is in state LISTEN, RESPOND (which in the implementation is the same as LISTEN), or REQUEST, since update_gsr() has not been called in these states, hence the sequence window is 0..0.
This patch fixes the problem by adding the REQUEST state as another exemption to the window check. The error reporting now works as expected on connecting.
--- net/dccp/ipv4.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/dccp/ipv4.c +1 -1
@@ -242,7 +242,7 @@ static void dccp_v4_err(struct sk_buff * dp =dccp_sk (sk); seq =dccp_hdr_seq (dh); -if (sk->sk_state !=DCCP_LISTEN && +if ((1 << sk->sk_state) & ~(DCCPF_REQUESTING |DCCPF_LISTEN ) && !between48 (seq, dp->dccps_swl, dp->dccps_swh)) {NET_INC_STATS_BH (LINUX_MIB_OUTOFWINDOWICMPS ); goto out;
Quoted 13 lines · Gerrit Renker
[DCCP]: One more exemption from full sequence number checks
This fixes the following problem: client connects to peer which has no DCCP enabled or loaded; ICMP error messages ("Protocol Unavailable") can be seen on the wire, but the application hangs. Reason: ICMP packets don't get through to
dccp_v4_err.When reporting errors, a sequence number check is made for the DCCP packet that had caused an ICMP error to arrive.
Such checks can not be made if the socket is in state LISTEN, RESPOND (which in the implementation is the same as LISTEN), or REQUEST, sinceupdate_gsr()has not been called in these states, hence the sequence window is 0..0.
Quoted 4 lines
This patch fixes the problem by adding the REQUEST state as another exemption to the window check. The error reporting now works as expected on connecting.
Signed-off-by Gerrit Renker <[email protected]>
Does this affect DCCP on IP v6? If it does, it should be fixed also. If it doesn't then can you add that to the changelog to stop others asking also.
| Does this affect DCCP on IP v6? If it does, it should be fixed also. | If it doesn't then can you add that to the changelog to stop others | asking also.
This patch is for IPv4 only - I have checked, dccp_v6_err uses a different mechanism, so the problem fixed by this patch does not seem to appear in IPv6 as well.
Must however admit that I haven't tested the IPv6 error reporting exhaustively (but will soon be doing more IPv6 apps), it would be good if others could test as well.
Quoted 13 lines · Gerrit Renker
[DCCP]: One more exemption from full sequence number checks
This fixes the following problem: client connects to peer which has no DCCP enabled or loaded; ICMP error messages ("Protocol Unavailable") can be seen on the wire, but the application hangs. Reason: ICMP packets don't get through to
dccp_v4_err.When reporting errors, a sequence number check is made for the DCCP packet that had caused an ICMP error to arrive.
Such checks can not be made if the socket is in state LISTEN, RESPOND (which in the implementation is the same as LISTEN), or REQUEST, sinceupdate_gsr()has not been called in these states, hence the sequence window is 0..0.
Quoted 4 lines
This patch fixes the problem by adding the REQUEST state as another exemption to the window check. The error reporting now works as expected on connecting.
Signed-off-by Gerrit Renker <[email protected]>