From: Kevin Wolf <kwolf@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/2] VHDX cleanup
Date: Mon, 7 Aug 2017 12:48:59 +0200 [thread overview]
Message-ID: <20170807104859.GC6578@localhost.localdomain> (raw)
In-Reply-To: <cover.1502075213.git.jcody@redhat.com>
Am 07.08.2017 um 05:08 hat Jeff Cody geschrieben:
> Two VHDX items cleaned up:
>
> 1. Check for error when calling bdrv_getlength() [Markus]
>
> 2. Check for overflow in offset prior to calling bdrv_truncate().
This doesn't look like cleanups to me, but like proper fixes. I think it
would still qualify for 2.10.
Kevin
prev parent reply other threads:[~2017-08-07 10:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 3:08 [Qemu-devel] [PATCH 0/2] VHDX cleanup Jeff Cody
2017-08-07 3:08 ` [Qemu-devel] [PATCH 1/2] block/vhdx: check error return of bdrv_getlength() Jeff Cody
2017-08-07 10:46 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-08-07 12:16 ` Jeff Cody
2017-08-07 11:25 ` [Qemu-devel] " Eric Blake
2017-08-07 3:08 ` [Qemu-devel] [PATCH 2/2] block/vhdx: check for offset overflow to bdrv_truncate() Jeff Cody
2017-08-07 10:48 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2017-08-07 11:24 ` [Qemu-devel] " Eric Blake
2017-08-07 12:13 ` Jeff Cody
2017-08-07 10:48 ` Kevin Wolf [this message]
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=20170807104859.GC6578@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=jcody@redhat.com \
--cc=qemu-block@nongnu.org \
--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).