From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:38742)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1TOUxi-00073W-4S
	for qemu-devel@nongnu.org; Wed, 17 Oct 2012 10:51:14 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1TOUxc-0007Et-Ds
	for qemu-devel@nongnu.org; Wed, 17 Oct 2012 10:51:10 -0400
Received: from mx1.redhat.com ([209.132.183.28]:32332)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1TOUxc-0007Ef-5m
	for qemu-devel@nongnu.org; Wed, 17 Oct 2012 10:51:04 -0400
Received: from int-mx01.intmail.prod.int.phx2.redhat.com
	(int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11])
	by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q9HEp37i007197
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <qemu-devel@nongnu.org>; Wed, 17 Oct 2012 10:51:03 -0400
Message-ID: <507EC5D2.4050500@redhat.com>
Date: Wed, 17 Oct 2012 16:50:58 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <1349877786-23514-1-git-send-email-pbonzini@redhat.com>
	<1349877786-23514-9-git-send-email-pbonzini@redhat.com>
	<87zk3lxiok.fsf@blackfin.pond.sub.org>
In-Reply-To: <87zk3lxiok.fsf@blackfin.pond.sub.org>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 08/25] migration (outgoing): add error
 propagation for all protocols
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com

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.

Paolo