qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: benoit.canet@irqsave.net, maxa@catit.be, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 00/21] block: Handle failure for potentially large allocations
Date: Fri, 8 Aug 2014 10:23:23 +0200	[thread overview]
Message-ID: <20140808082323.GB4118@noname.redhat.com> (raw)
In-Reply-To: <53E3C6B3.5030300@redhat.com>

Am 07.08.2014 um 20:34 hat Max Reitz geschrieben:
> On 24.06.2014 17:36, Kevin Wolf wrote:
> >A not too small part of the recent CVEs were DoS scenarios by letting
> >qemu abort with too large memory allocations. We generally "fixed" these
> >cases by setting some limits on values read from image files that
> >influence the size of allocations.
> >
> >Because we still need to allow reading large images, this works only to
> >a certain degree and we still can get fairly large allocations, which
> >are not unthinkable to fail on some machines.
> >
> >This series converts potentially large allocations to g_try_malloc() and
> >friends and handles failure gracefully e.g. by returning -ENOMEM. This
> >may cause hot-plug of a new disk or individual requests to fail, but the
> >VM as a whole can keep running.
> 
> Ping – is there anything missing here? This series does contain one
> patch from me, so I'm naturally interested in seeing this series
> getting merged. ;-)

Whoops, thanks for the reminder. I completely forgot about this series.
Applied it to the block branch now.

Kevin

  reply	other threads:[~2014-08-08  8:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 15:36 [Qemu-devel] [PATCH v4 00/21] block: Handle failure for potentially large allocations Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 01/21] block: Introduce qemu_try_blockalign() Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 02/21] block: Handle failure for potentially large allocations Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 03/21] bochs: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 04/21] cloop: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 05/21] curl: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 06/21] dmg: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 07/21] iscsi: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 08/21] nfs: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 09/21] parallels: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 10/21] qcow1: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 11/21] qcow2: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 12/21] qed: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 13/21] raw-posix: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 14/21] raw-win32: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 15/21] rbd: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 16/21] vdi: " Kevin Wolf
2014-06-24 15:36 ` [Qemu-devel] [PATCH v4 17/21] vhdx: " Kevin Wolf
2014-06-24 15:37 ` [Qemu-devel] [PATCH v4 18/21] vmdk: " Kevin Wolf
2014-06-24 15:37 ` [Qemu-devel] [PATCH v4 19/21] vpc: " Kevin Wolf
2014-06-24 15:37 ` [Qemu-devel] [PATCH v4 20/21] mirror: " Kevin Wolf
2014-06-24 15:37 ` [Qemu-devel] [PATCH v4 21/21] qcow2: Return useful error code in refcount_init() Kevin Wolf
2014-08-07 18:34 ` [Qemu-devel] [PATCH v4 00/21] block: Handle failure for potentially large allocations Max Reitz
2014-08-08  8:23   ` Kevin Wolf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-05 13:36 Kevin Wolf
2014-06-11 10:33 ` Stefan Hajnoczi
2014-06-11 14:36 ` Stefan Hajnoczi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140808082323.GB4118@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=maxa@catit.be \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).