qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: kwolf@redhat.com, jcody@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v7 00/13] curl: fix curl read
Date: Fri, 7 Jun 2013 15:47:23 +0800	[thread overview]
Message-ID: <20130607074723.GA26941@localhost.nay.redhat.com> (raw)
In-Reply-To: <20130607072707.GP4515@redhat.com>

On Fri, 06/07 08:27, Richard W.M. Jones wrote:
> On Fri, Jun 07, 2013 at 09:54:42AM +0800, Fam Zheng wrote:
> > The weird thing is it doesn't work for me, I'm sure something is wrong
> > with current upstream, although not totally broken.
> > 
> >   $./qemu-io http://localhost/vm/arch.raw -c 'read -v 0 512'
> >   (stuck here forever, no output)
> 
> This doesn't work for me either.
> 
> *However* it only doesn't work if I use the Fedora version of curl,
> which I'm convinced is broken.

I see, it turns out upstream curl works in my case too, thanks.

So it's more of curl broken rather than qemu driver. For the timeout
issue introduced here, I think it's the effect of implementing timer in
the driver, I can't think of a good way to workaround. However the
master code not using timer at all is an undocumented usage of libcurl.

-- 
Fam

  reply	other threads:[~2013-06-07  7:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  6:25 [Qemu-devel] [PATCH v7 00/13] curl: fix curl read Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 01/13] curl: introduce CURLSockInfo to BDRVCURLState Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 02/13] curl: change magic number to sizeof Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 03/13] curl: change curl_multi_do to curl_fd_handler Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 04/13] curl: fix curl_open Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 05/13] curl: add timer to BDRVCURLState Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 06/13] curl: introduce CURLDataCache Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 07/13] curl: make use of CURLDataCache Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 08/13] curl: use list to store CURLState Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 09/13] curl: add cache quota Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 10/13] curl: introduce ssl_no_cert runtime option Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 11/13] block/curl.c: Refuse to open the handle for writes Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 12/13] curl: set s->url to NULL after free Fam Zheng
2013-06-06  6:25 ` [Qemu-devel] [PATCH v7 13/13] curl: change timeout to 30 seconds Fam Zheng
2013-06-06 11:01 ` [Qemu-devel] [PATCH v7 00/13] curl: fix curl read Richard W.M. Jones
2013-06-07  1:54   ` Fam Zheng
2013-06-07  7:27     ` Richard W.M. Jones
2013-06-07  7:47       ` Fam Zheng [this message]
2013-06-07  9:41         ` Richard W.M. Jones
2013-06-07  7:46   ` Stefan Hajnoczi
2013-06-07  7:53     ` 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=20130607074723.GA26941@localhost.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --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).