From: "Richard W.M. Jones" <rjones@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 00/10] curl: fix curl read
Date: Wed, 22 May 2013 12:12:24 +0100 [thread overview]
Message-ID: <20130522111224.GS4515@redhat.com> (raw)
In-Reply-To: <519CA653.3090803@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On Wed, May 22, 2013 at 01:04:51PM +0200, Paolo Bonzini wrote:
> Something is trying to write, but there's no write operation defined for
> CURL.
>
> I guess curl (and other backends too) should reject being opened for
> write. Alternatively, block.c could do that for them.
Yes, I'd just got to that conclusion as well :-)
The attached patch fixes the crash for me.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
[-- Attachment #2: 0001-block-curl.c-Refuse-to-open-the-handle-for-writes.patch --]
[-- Type: text/plain, Size: 771 bytes --]
From 0d42755f009c142b85fb07a06a41cee6c7ea68ba Mon Sep 17 00:00:00 2001
From: "Richard W.M. Jones" <rjones@redhat.com>
Date: Wed, 22 May 2013 12:11:45 +0100
Subject: [PATCH] block/curl.c: Refuse to open the handle for writes.
---
block/curl.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/block/curl.c b/block/curl.c
index b8935fd..f1e302b 100644
--- a/block/curl.c
+++ b/block/curl.c
@@ -406,6 +406,10 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags)
static int inited = 0;
+ if (flags & BDRV_O_RDWR) {
+ return -ENOTSUP;
+ }
+
opts = qemu_opts_create_nofail(&runtime_opts);
qemu_opts_absorb_qdict(opts, options, &local_err);
if (error_is_set(&local_err)) {
--
1.8.2.1
next prev parent reply other threads:[~2013-05-22 11:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 3:16 [Qemu-devel] [PATCH v4 00/10] curl: fix curl read Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 01/10] curl: introduce CURLSockInfo to BDRVCURLState Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 02/10] curl: change magic number to sizeof Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 03/10] curl: change curl_multi_do to curl_fd_handler Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 04/10] curl: fix curl_open Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 05/10] curl: add timer to BDRVCURLState Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 06/10] curl: introduce CURLDataCache Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 07/10] curl: make use of CURLDataCache Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 08/10] curl: use list to store CURLState Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 09/10] curl: add cache quota Fam Zheng
2013-05-22 3:16 ` [Qemu-devel] [PATCH v4 10/10] curl: introduce ssl_no_cert runtime option Fam Zheng
2013-05-22 9:32 ` [Qemu-devel] [PATCH v4 00/10] curl: fix curl read Fam Zheng
2013-05-22 9:44 ` Richard W.M. Jones
2013-05-22 11:04 ` Paolo Bonzini
2013-05-22 11:12 ` Richard W.M. Jones [this message]
2013-05-22 14:39 ` Stefan Hajnoczi
2013-05-23 0:38 ` Fam Zheng
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=20130522111224.GS4515@redhat.com \
--to=rjones@redhat.com \
--cc=famz@redhat.com \
--cc=pbonzini@redhat.com \
--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).