Re: [Qemu-devel] [PATCH 1/6] Terminate emulation on memory allocation failure

["Daniel P. Berrange" <berrange@redhat.com>]

On Thu, Feb 05, 2009 at 01:08:41PM +0200, Avi Kivity wrote:
> Memory allocation failures are a very rare condition on virtual-memory
> hosts.  They are also very difficult to handle correctly (especially in a
> hardware emulation context).  Because of this, it is better to gracefully
> terminate emulation rather than executing untested or even unwritten recovery
> code paths.
> 
> This patch changes the qemu memory allocation routines to terminate emulation
> if an allocation failure is encountered.
> 
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
>  qemu-malloc.c |   16 ++++++++++------
>  1 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/qemu-malloc.c b/qemu-malloc.c
> index dc74efe..1d00f26 100644
> --- a/qemu-malloc.c
> +++ b/qemu-malloc.c
> @@ -22,6 +22,14 @@
>   * THE SOFTWARE.
>   */
>  #include "qemu-common.h"
> +#include <stdlib.h>
> +
> +static void *oom_check(void *ptr)
> +{
> +    if (ptr == NULL)
> +        exit(13);
> +    return ptr;
> +}

Will all our atexit handlers cope with OOM too? In particular
we don't want them calling qemu_malloc again, or this becomes
re-entrant. If we want to go down this route, then abort() is
probably safer.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|