From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NHaKC-0008D9-QJ
	for qemu-devel@nongnu.org; Mon, 07 Dec 2009 04:56:12 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NHaK9-0008C5-3E
	for qemu-devel@nongnu.org; Mon, 07 Dec 2009 04:56:12 -0500
Received: from [199.232.76.173] (port=40152 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NHaK8-0008Br-Nx
	for qemu-devel@nongnu.org; Mon, 07 Dec 2009 04:56:08 -0500
Received: from lo.gmane.org ([80.91.229.12]:48409)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <gceq-qemu-devel@m.gmane.org>)
	id 1NHaK8-0002jZ-A6
	for qemu-devel@nongnu.org; Mon, 07 Dec 2009 04:56:08 -0500
Received: from list by lo.gmane.org with local (Exim 4.50) id 1NHaK6-0001j4-0h
	for qemu-devel@nongnu.org; Mon, 07 Dec 2009 10:56:06 +0100
Received: from 85.93.118.17 ([85.93.118.17])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <qemu-devel@nongnu.org>; Mon, 07 Dec 2009 10:56:06 +0100
Received: from pbonzini by 85.93.118.17 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <qemu-devel@nongnu.org>; Mon, 07 Dec 2009 10:56:06 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Mon, 07 Dec 2009 10:55:43 +0100
Message-ID: <hfijev$gig$1@ger.gmane.org>
References: <m3skbwxgkp.fsf@crossbow.pond.sub.org>	<4B193DA5.6040507@codemonkey.ws>
	<4B1A9359.8080305@redhat.com>	<4B1A9811.8020108@codemonkey.ws>	<m3vdgky0za.fsf@crossbow.pond.sub.org>	<4B1BE153.6070509@collabora.co.uk>
	<4B1BE691.1010401@redhat.com>	<Pine.LNX.4.64.0912062039420.4300@linmac.oyster.ru>	<4B1BF1A0.4030002@redhat.com>
	<4B1C3282.70009@collabora.co.uk>	<20091207025156.GD1021@shareable.org>
	<4B1CCD4F.3030003@collabora.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
In-Reply-To: <4B1CCD4F.3030003@collabora.co.uk>
Sender: news <news@ger.gmane.org>
Subject: [Qemu-devel] Re: [PATCH] Permit zero-sized qemu_malloc() & friends
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 12/07/2009 10:39 AM, Ian Molton wrote:
> Send what message to the host? If the malloc in the socet reconnect code
> fails, its the code on the host thats going to flag up that malloc failed.

He means to management code.

>> >  and if it does manage to receive the message, you can be almost
>> >  certain that it won't be able to run any GUI operations, send mail,
>> >  etc. to inform the admin.
>
> OTOH, If all it does it log it to a file, theres a fair chance it might
> succeed.

Not necessarily, for example fprintf may fail.  There _may_ be a fair 
chance to succeed if you use write(2) directly, but that's it basically, 
and ENOMEM is always there waiting for you...

Paolo