From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: jcody@redhat.com, mreitz@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 0/9] raw: Prohibit dangerous writes for probed images
Date: Wed, 26 Nov 2014 16:23:50 +0000 [thread overview]
Message-ID: <20141126162350.GG14288@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1416497234-29880-1-git-send-email-kwolf@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4289 bytes --]
On Thu, Nov 20, 2014 at 04:27:05PM +0100, Kevin Wolf wrote:
> See the commit message of patch 7 for the why and how. This series
> will probably be only part of the solution and doesn't mean that we
> should stop looking for other patches which improve different parts of
> the problem.
>
> See the mailing list thread "Image probing: how it can be insecure, and
> what we could do about it" for the complete context.
>
> v3:
> - Patch 5/6: Improved function comment [Max]
> - Patch 7: Handle nb_sectors == 0 case [Stefan]
> - Patch 7: Even longer error message [Eric]
> - Patch 9: Don't create a vhdx image in a test for raw, it might not be
> compiled in. Use sample images instead, including the more exotic formats.
> Add a new sample image containing a GRUB MBR. [Max, Eric]
>
> v2:
> - Fixed offset in qemu_iovec_concat [Kevin]
> - Added paragraph to patch 7 explaining that we're not breaking
> additional cases, but only change the failure mode of already
> broken scenarios [Max]
> - Added a warning when opening an image in "restricted raw" mode,
> which required a few more patches to make the test cases avoid
> this warning [Markus]
>
>
> Kevin Wolf (8):
> qemu-io: Allow explicitly specifying format
> qemu-iotests: Use qemu-io -f $IMGFMT
> qemu-iotests: Add qemu-io format option in Python tests
> qtests: Specify image format explicitly
> block: Read only one sector for format probing
> raw: Prohibit dangerous writes for probed images
> qemu-iotests: Fix stderr handling in common.qemu
> qemu-iotests: Test writing non-raw image headers to raw image
>
> Markus Armbruster (1):
> block: Factor bdrv_probe_all() out of find_image_format()
>
> block.c | 51 +++--
> block/raw_bsd.c | 64 +++++-
> include/block/block_int.h | 5 +
> qemu-io.c | 28 ++-
> tests/ahci-test.c | 3 +-
> tests/bios-tables-test.c | 2 +-
> tests/drive_del-test.c | 2 +-
> tests/fdc-test.c | 2 +-
> tests/hd-geo-test.c | 2 +-
> tests/i440fx-test.c | 5 +-
> tests/ide-test.c | 9 +-
> tests/nvme-test.c | 2 +-
> tests/qemu-iotests/016 | 11 +-
> tests/qemu-iotests/030 | 22 +--
> tests/qemu-iotests/040 | 32 +--
> tests/qemu-iotests/048 | 2 +-
> tests/qemu-iotests/055 | 18 +-
> tests/qemu-iotests/058 | 11 +-
> tests/qemu-iotests/071 | 10 +-
> tests/qemu-iotests/071.out | 6 +-
> tests/qemu-iotests/077 | 2 +-
> tests/qemu-iotests/081 | 8 +-
> tests/qemu-iotests/081.out | 2 +-
> tests/qemu-iotests/089 | 6 +-
> tests/qemu-iotests/109 | 132 +++++++++++++
> tests/qemu-iotests/109.out | 231 ++++++++++++++++++++++
> tests/qemu-iotests/common | 2 +-
> tests/qemu-iotests/common.qemu | 3 +-
> tests/qemu-iotests/group | 1 +
> tests/qemu-iotests/sample_images/grub_mbr.raw.bz2 | Bin 0 -> 552 bytes
> tests/usb-hcd-uhci-test.c | 2 +-
> tests/usb-hcd-xhci-test.c | 2 +-
> tests/virtio-blk-test.c | 4 +-
> tests/virtio-scsi-test.c | 4 +-
> 34 files changed, 584 insertions(+), 102 deletions(-)
> create mode 100755 tests/qemu-iotests/109
> create mode 100644 tests/qemu-iotests/109.out
> create mode 100644 tests/qemu-iotests/sample_images/grub_mbr.raw.bz2
>
> --
> 1.8.3.1
>
>
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-11-26 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 15:27 [Qemu-devel] [PATCH v3 0/9] raw: Prohibit dangerous writes for probed images Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 1/9] qemu-io: Allow explicitly specifying format Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 2/9] qemu-iotests: Use qemu-io -f $IMGFMT Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 3/9] qemu-iotests: Add qemu-io format option in Python tests Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 4/9] qtests: Specify image format explicitly Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 5/9] block: Factor bdrv_probe_all() out of find_image_format() Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 6/9] block: Read only one sector for format probing Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 7/9] raw: Prohibit dangerous writes for probed images Kevin Wolf
2014-11-20 20:08 ` Dr. David Alan Gilbert
2014-11-21 10:15 ` Kevin Wolf
2014-11-21 10:26 ` Dr. David Alan Gilbert
2014-11-25 16:51 ` Stefan Hajnoczi
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 8/9] qemu-iotests: Fix stderr handling in common.qemu Kevin Wolf
2014-11-20 15:27 ` [Qemu-devel] [PATCH v3 9/9] qemu-iotests: Test writing non-raw image headers to raw image Kevin Wolf
2014-11-20 16:18 ` Max Reitz
2014-11-20 16:29 ` Kevin Wolf
2014-11-26 16:23 ` Stefan Hajnoczi [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=20141126162350.GG14288@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=armbru@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--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).