tree d9a101aadfe2d190fad0e16e6df0c0c815179719
parent d691180e41f58cc3c1f9fa848c2ab89193503160
author Luiz Capitulino <lcapitulino@redhat.com> 1348244275 -0300
committer Luiz Capitulino <lcapitulino@redhat.com> 1348749977 -0300

qmp: dump-guest-memory: don't spin if non-blocking fd would block

fd_write_vmcore() will indefinitely spin for a non-blocking
file-descriptor that would block. However, if the fd is non-blocking,
how does it make sense to spin?

Change this behavior to return an error instead.

Note that this can only happen with an fd provided by a management
application. The fd opened internally by dump-guest-memory is blocking.

While there, also fix 'writen_size' variable name.

Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>