|
From: | Markus Armbruster |
Subject: | Re: [Qemu-devel] [PATCH 08/25] migration (outgoing): add error propagation for all protocols |
Date: | Wed, 17 Oct 2012 17:43:45 +0200 |
User-agent: | Gnus/5.13 (Gnus v5.13) Emacs/24.1 (gnu/linux) |
Paolo Bonzini <address@hidden> writes: > Il 17/10/2012 16:43, Markus Armbruster ha scritto: >>> > Error propagation is already there for socket backends, even though >>> > it is (and remains) incomplete because no Error is passed to the >>> > NonBlockingConnectHandler. >> Why is that a problem? > > It means that the exact error message still cannot be sent to the user > if the OS reports it asynchronously via SO_ERROR. If > NonBlockingConnectHandler received an Error**, we could for example > report the error class and/or message via a new field of the > query-migration command even if it is reported asynchronously. First time you mention the problem in a commit message could use a variant of this explanation.
[Prev in Thread] | Current Thread | [Next in Thread] |