From: Kevin Wolf <kwolf@redhat.com>
To: aurelien@aurel32.net
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [STABLE][PULL 00/10] Patches for 0.12.4
Date: Fri, 9 Apr 2010 11:46:18 +0200 [thread overview]
Message-ID: <1270806388-28138-1-git-send-email-kwolf@redhat.com> (raw)
Hi Aurelien,
I went through the patches that were committed recently, either written by me
or concerning block stuff (most of them are both). I came up with this list of
patches that should go into 0.12.4. The first half of them is contained in
current master (you'll see the cherry-pick line in the commit log for those),
the rest has already been posted to the list, but is still sitting in my block
queue and waiting for Anthony's return.
Kevin
The following changes since commit 804b6ab08d82adcab05d64362be91c48a7467fd4:
Paul Brook (1):
UHCI spurious interrut fix
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-aurelien-0.12
Christoph Hellwig (1):
block: avoid creating too large iovecs in multiwrite_merge
Gerd Hoffmann (1):
scsi-disk: fix buffer overflow
Kevin Wolf (8):
json-parser: Fix segfault on malformed input
qcow2: Factor next_refcount_table_size out
qcow2: Rewrite alloc_refcount_block/grow_refcount_table
block: Fix multiwrite error handling
block: Fix error code in multiwrite for immediate failures
block: Fix multiwrite memory leak in error case
qcow2: Don't ignore immediate read/write failures
qcow2: Remove request from in-flight list after error
block.c | 11 +-
block/qcow2-cluster.c | 1 +
block/qcow2-refcount.c | 334 ++++++++++++++++++++++++++++++++++--------------
block/qcow2.c | 14 ++-
hw/scsi-disk.c | 4 +-
json-parser.c | 2 +-
qemu-common.h | 4 +
7 files changed, 266 insertions(+), 104 deletions(-)
next reply other threads:[~2010-04-09 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-09 9:46 Kevin Wolf [this message]
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 01/10] json-parser: Fix segfault on malformed input Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 02/10] block: avoid creating too large iovecs in multiwrite_merge Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 03/10] qcow2: Factor next_refcount_table_size out Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 04/10] qcow2: Rewrite alloc_refcount_block/grow_refcount_table Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 05/10] scsi-disk: fix buffer overflow Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 06/10] block: Fix multiwrite error handling Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 07/10] block: Fix error code in multiwrite for immediate failures Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 08/10] block: Fix multiwrite memory leak in error case Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 09/10] qcow2: Don't ignore immediate read/write failures Kevin Wolf
2010-04-09 9:46 ` [Qemu-devel] [STABLE][PATCH 10/10] qcow2: Remove request from in-flight list after error Kevin Wolf
2010-04-09 16:47 ` [Qemu-devel] [STABLE][PULL 00/10] Patches for 0.12.4 Aurelien Jarno
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=1270806388-28138-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
/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).