On Thu, Jun 05, 2014 at 03:55:40AM +0200, Paolo Bonzini wrote:
Il 05/06/2014 00:33, Hani Benhabiles ha scritto:
IIUC, what this does is ensure that the other side gets a FIN before it
gets
a RST. Is this correct?
Yes. Without shutdown(), this could be reproduced (unreliably) on
Il 05/06/2014 11:58, Hani Benhabiles ha scritto:
On Thu, Jun 05, 2014 at 03:55:40AM +0200, Paolo Bonzini wrote:
Il 05/06/2014 00:33, Hani Benhabiles ha scritto:
IIUC, what this does is ensure that the other side gets a FIN before it gets
a RST. Is this correct?
Yes. Without shutdown(), this
On Tue, Jun 03, 2014 at 01:33:41PM +0200, Paolo Bonzini wrote:
Il 31/05/2014 23:39, Hani Benhabiles ha scritto:
This forces finishing data sending to client before closing the socket like
in
exports listing or replying with NBD_REP_ERR_UNSUP cases.
Signed-off-by: Hani Benhabiles
Il 05/06/2014 00:33, Hani Benhabiles ha scritto:
IIUC, what this does is ensure that the other side gets a FIN before it gets
a RST. Is this correct?
Yes. Without shutdown(), this could be reproduced (unreliably) on multiple
tries. This is done in nbd_client_close() too, for the same reasons
Il 31/05/2014 23:39, Hani Benhabiles ha scritto:
This forces finishing data sending to client before closing the socket like in
exports listing or replying with NBD_REP_ERR_UNSUP cases.
Signed-off-by: Hani Benhabiles h...@linux.com
---
blockdev-nbd.c | 1 +
qemu-nbd.c | 1 +
2 files
This forces finishing data sending to client before closing the socket like in
exports listing or replying with NBD_REP_ERR_UNSUP cases.
Signed-off-by: Hani Benhabiles h...@linux.com
---
blockdev-nbd.c | 1 +
qemu-nbd.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/blockdev-nbd.c
