aboutgitcodebugslistschat
path: root/test
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2022-11-30 15:13:10 +1100
committerStefano Brivio <sbrivio@redhat.com>2022-12-06 07:41:45 +0100
commit71d2595a8f045a7b7bc51e4a9472d5eb540fe079 (patch)
treec1222b1fdc7593570faf87c9ed659383b13d3bf8 /test
parent7610034fefcfbac4665756ef856d69a1780c80e7 (diff)
downloadpasst-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.tar
passt-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.tar.gz
passt-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.tar.bz2
passt-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.tar.lz
passt-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.tar.xz
passt-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.tar.zst
passt-71d2595a8f045a7b7bc51e4a9472d5eb540fe079.zip
udp: Update UDP "connection" timestamps in both directions
A UDP pseudo-connection between port A in the init namespace and port B in the pasta guest namespace involves two sockets: udp_splice_init[v6][B] and udp_splice_ns[v6][A]. The socket which originated this "connection" will be permanent but the other one will be closed on a timeout. When we get a packet from the originating socket, we update the timeout on the other socket, but we don't do the same when we get a reply packet from the other socket. However any activity on the "connection" probably indicates that it's still in use. Without this we could incorrectly time out a "connection" if it's using a protocol which involves a single initiating packet, but which then gets continuing replies from the target. Correct this by updating the timeout on both sockets for a packet in either direction. This also updates the timestamps for the permanent originating sockets which is unnecessary, but harmless. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'test')
0 files changed, 0 insertions, 0 deletions