diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2024-11-06 14:03:22 +1100 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2024-11-07 12:47:30 +0100 |
| commit | 1699083f291ca8e639d0711eff59c61eecdf02c1 (patch) | |
| tree | 78e465d06825069a9961a4b36d116b87ecd1fd5e /tcp_vu.c | |
| parent | b456ee1b53171c46b6f25c1c43d9fc17f6116745 (diff) | |
| download | passt-1699083f291ca8e639d0711eff59c61eecdf02c1.tar passt-1699083f291ca8e639d0711eff59c61eecdf02c1.tar.gz passt-1699083f291ca8e639d0711eff59c61eecdf02c1.tar.bz2 passt-1699083f291ca8e639d0711eff59c61eecdf02c1.tar.lz passt-1699083f291ca8e639d0711eff59c61eecdf02c1.tar.xz passt-1699083f291ca8e639d0711eff59c61eecdf02c1.tar.zst passt-1699083f291ca8e639d0711eff59c61eecdf02c1.zip | |
test: Make nstool hold robust against interruptions to control clients
Currently nstool die()s on essentially any error. In most cases that's
fine for our purposes. However, it's a problem when in "hold" mode and
getting an IO error on an accept()ed socket. This could just indicate that
the control client aborted prematurely, in which case we don't want to
kill of the namespace we're holding.
Adjust these to print an error, close() the control client socket and
carry on. In addition, we need to explicitly ignore SIGPIPE in order not
to be killed by an abruptly closed client connection.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'tcp_vu.c')
0 files changed, 0 insertions, 0 deletions