diff options
author | Max Reitz <mreitz@redhat.com> | 2017-06-11 14:37:14 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2017-06-15 11:04:05 +0200 |
commit | 041e32b8d9d076980b4e35317c0339e57ab888f1 (patch) | |
tree | a75e5f82c44a4c87d9294c85af14954b3939a918 /util/qemu-option.c | |
parent | 0c9390d978cbf61e8f16c9f580fa96b305c43568 (diff) | |
download | qemu-041e32b8d9d076980b4e35317c0339e57ab888f1.zip qemu-041e32b8d9d076980b4e35317c0339e57ab888f1.tar.gz qemu-041e32b8d9d076980b4e35317c0339e57ab888f1.tar.bz2 |
qemu-nbd: Ignore SIGPIPE
qemu proper has done so for 13 years
(8a7ddc38a60648257dc0645ab4a05b33d6040063), qemu-img and qemu-io have
done so for four years (526eda14a68d5b3596be715505289b541288ef2a).
Ignoring this signal is especially important in qemu-nbd because
otherwise a client can easily take down the qemu-nbd server by dropping
the connection when the server wants to send something, for example:
$ qemu-nbd -x foo -f raw -t null-co:// &
[1] 12726
$ qemu-io -c quit nbd://localhost/bar
can't open device nbd://localhost/bar: No export with name 'bar' available
[1] + 12726 broken pipe qemu-nbd -x foo -f raw -t null-co://
In this case, the client sends an NBD_OPT_ABORT and closes the
connection (because it is not required to wait for a reply), but the
server replies with an NBD_REP_ACK (because it is required to reply).
Signed-off-by: Max Reitz <mreitz@redhat.com>
Message-Id: <20170611123714.31292-1-mreitz@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'util/qemu-option.c')
0 files changed, 0 insertions, 0 deletions