diff options
Diffstat (limited to 'test/packetdrill/tests/linux/close')
3 files changed, 104 insertions, 0 deletions
diff --git a/test/packetdrill/tests/linux/close/close-read-data-fin.pkt b/test/packetdrill/tests/linux/close/close-read-data-fin.pkt new file mode 100644 index 0000000..bad95c2 --- /dev/null +++ b/test/packetdrill/tests/linux/close/close-read-data-fin.pkt @@ -0,0 +1,38 @@ +// If we close the connection after read()'ing what +// the other side sent, a FIN will be generated. This +// behavior conforms to RFC 793. + +0.000 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3 +0.000 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 +0.000 bind(3, ..., ...) = 0 +0.000 listen(3, 1) = 0 + +0.100 < S 0:0(0) win 32792 <mss 1460,sackOK,nop,nop,nop,wscale 7> +0.100 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK,nop,wscale 6> +0.200 < . 1:1(0) ack 1 win 257 +0.200 accept(3, ..., ...) = 4 + +// Receive first segment +0.210 < P. 1:1001(1000) ack 1 win 46 + +// Send one ACK +0.210 > . 1:1(0) ack 1001 + +// Application writes 1000 bytes +0.250 write(4, ..., 1000) = 1000 +0.250 > P. 1:1001(1000) ack 1001 + +// ACK +0.300 < . 1001:1001(0) ack 1001 win 257 + +0.400 read(4, ..., 1000) = 1000 + +// Client closes the connection +0.610 < F. 1001:1001(0) ack 1001 win 260 + +// Respond with (delayed) ACK +0.650 > . 1001:1001(0) ack 1002 + +// We close the connection +0.700 close(4) = 0 +0.701 > F. 1001:1001(0) ack 1002 diff --git a/test/packetdrill/tests/linux/close/close-so-linger-onoff-1-linger-0-rst.pkt b/test/packetdrill/tests/linux/close/close-so-linger-onoff-1-linger-0-rst.pkt new file mode 100644 index 0000000..dcec1cf --- /dev/null +++ b/test/packetdrill/tests/linux/close/close-so-linger-onoff-1-linger-0-rst.pkt @@ -0,0 +1,28 @@ +// Verify that when a process uses SO_LINGER with {onoff=1, linger=0}, +// and then closes the socket, the kernel sends a RST. +// (TODO(ncardwell): it also frees the socket immediately without any +// time in TIME_WAIT; we should test this too once we have some +// infrastructure for testing this kind of thing reliably...) + +// Initialize a server socket. +0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3 ++0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 ++0 bind(3, ..., ...) = 0 ++0 listen(3, 1) = 0 + ++0 < S 0:0(0) win 32792 <mss 1000,sackOK,nop,nop,nop,wscale 7> ++0 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK,nop,wscale 6> ++0 < . 1:1(0) ack 1 win 257 + ++0 accept(3, ..., ...) = 4 + ++0 setsockopt(4, SOL_SOCKET, SO_LINGER, {onoff=1, linger=0}, 8) = 0 + +// Write some data, receive an ACK. ++0 write(4, ..., 1000) = 1000 ++0 > P. 1:1001(1000) ack 1 ++0 < . 1:1(0) ack 1001 win 257 + +// Clean up. ++0 close(4) = 0 ++0 > R. 1001:1001(0) ack 1 diff --git a/test/packetdrill/tests/linux/close/close-unread-data-rst.pkt b/test/packetdrill/tests/linux/close/close-unread-data-rst.pkt new file mode 100644 index 0000000..d30808b --- /dev/null +++ b/test/packetdrill/tests/linux/close/close-unread-data-rst.pkt @@ -0,0 +1,38 @@ +// If we close the connection before read()'ing what +// the other side sent, a RST will be generated instead +// of a FIN. + +0.000 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3 +0.000 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0 +0.000 bind(3, ..., ...) = 0 +0.000 listen(3, 1) = 0 + +0.100 < S 0:0(0) win 32792 <mss 1460,sackOK,nop,nop,nop,wscale 7> +0.100 > S. 0:0(0) ack 1 <mss 1460,nop,nop,sackOK,nop,wscale 6> +0.200 < . 1:1(0) ack 1 win 257 +0.200 accept(3, ..., ...) = 4 + +// Receive first segment. +0.210 < P. 1:1001(1000) ack 1 win 46 + +// Send one ACK. +0.210 > . 1:1(0) ack 1001 + +// Application writes 1000 bytes. +0.250 write(4, ..., 1000) = 1000 +0.250 > P. 1:1001(1000) ack 1001 + +// ACK +0.300 < . 1001:1001(0) ack 1001 win 257 + +// Client closes the connection. +0.610 < F. 1001:1001(0) ack 1001 win 260 + +// Respond with (delayed) ACK. +0.650 > . 1001:1001(0) ack 1002 + +// We close the connection. +0.700 close(4) = 0 +// Since we have not read, we generate a RST instead of a FIN +// conforming to RFC 1122 section 4.2.2.13. +0.701 > R. 1001:1001(0) ack 1002 |