aboutgitcodebugslistschat
path: root/contrib/qemu
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2026-05-28 15:02:07 +1000
committerStefano Brivio <sbrivio@redhat.com>2026-06-04 06:35:16 +0200
commit1d475b1dbf22dac4a9fda3ebb444b0343392c5c3 (patch)
tree3c057b9e3d165444f4863f996f3ea9ce8251c076 /contrib/qemu
parent630e9bf1decf94618a036a020b7c920c8ab6126c (diff)
downloadpasst-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.tar
passt-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.tar.gz
passt-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.tar.bz2
passt-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.tar.lz
passt-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.tar.xz
passt-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.tar.zst
passt-1d475b1dbf22dac4a9fda3ebb444b0343392c5c3.zip
tcp_splice: Simplify EPOLLRDHUP / eof / FIN handling
There are two ways we can tell one of our sockets has received a FIN. We can either see an EPOLLRDHUP epoll event, or we can get a zero-length read (EOF) on the socket. We currently use both, in a mildly confusing way: we only set the FIN_RCVD() flag based on the EPOLLRDHUP event, but then some other close out logic is based on seeing an EOF. Simplify this by setting the flag based on only the EOF. To make sure we don't miss an event if we get an EPOLLRDHUP with no data, we trigger the forwarding path for EPOLLRDHUP as well as EPOLLIN. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib/qemu')
0 files changed, 0 insertions, 0 deletions