qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org, stefanha@redhat.com, kwolf@redhat.com,
	jcody@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 00/12] curl: fix curl read
Date: Mon, 27 May 2013 12:57:20 +0100	[thread overview]
Message-ID: <20130527115720.GW4515@redhat.com> (raw)
In-Reply-To: <20130527022521.GA27700@localhost.nay.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2718 bytes --]

On Mon, May 27, 2013 at 10:25:21AM +0800, Fam Zheng wrote:
> On Fri, 05/24 09:07, Richard W.M. Jones wrote:
> > On Fri, May 24, 2013 at 01:36:55PM +0800, Fam Zheng wrote:
> > > Changes from v5:
> > >   05: Rename bs to s for BDRVCURLState.
> > >   06: Use int64_t for offsets.
> > >       Fix printf format string.
> > >       Move introducing of use_count to 07.
> > >   07: Drop explicit cast.
> > >       Use int64_t for offsets.
> > >       Use_count moved here.
> > >   08: Remove duplicated.
> > >       Move s->url = NULL to separate patch.
> > >   09: Fix while(0);
> > >   12: Added:
> > >       curl: set s->url to NULL after free.
> > 
> > This patch is definitely not working.  The guest sees loads of
> > disk errors like this:
> > 
> > [   30.880265] sd 2:0:0:0: [sda]  
> > [   30.880265] Add. Sense: I/O process terminated
> > [   30.880265] sd 2:0:0:0: [sda] CDB: 
> > [   30.880265] Read(10): 28 00 00 bf b0 87 00 00 01 00
> > [   32.030702] sd 2:0:0:0: [sda]  
> > [   32.031663] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > [   32.031663] sd 2:0:0:0: [sda]  
> > [   32.031663] Sense Key : Aborted Command [current] 
> > [   32.031663] sd 2:0:0:0: [sda]  
> > [   32.031663] Add. Sense: I/O process terminated
> > [   32.031663] sd 2:0:0:0: [sda] CDB: 
> > [   32.031663] Read(10): 28 00 00 00 08 46 00 00 01 00
> > [   32.031663] blk_update_request: 32 callbacks suppressed
> > [   32.031663] end_request: I/O error, dev sda, sector 2118
> > [   32.031663] quiet_error: 46 callbacks suppressed
> > [   32.031663] Buffer I/O error on device sda1, logical block 2055
> > [   32.031663] sd 2:0:0:0: [sda]  
> > [   32.031663] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> > [   32.031663] sd 2:0:0:0: [sda]  
> > [   32.031663] Sense Key : Aborted Command [current] 
> > [   32.031663] sd 2:0:0:0: [sda]  
> > [   32.031663] Add. Sense: I/O process terminated
> > [   32.031663] sd 2:0:0:0: [sda] CDB: 
> > [   32.031663] Read(10): 28 00 00 00 08 45 00 00 01 00
> > [   32.031663] end_request: I/O error, dev sda, sector 2117
> > [   32.031663] Buffer I/O error on device sda1, logical block 2054
> > [   32.031663] sd 2:0:0:0: [sda]  
> > 
> 
> Rich, are you testing with libguestfs or qemu? Since I can't get
> libguestfs run with your patch to refuse writable open.

You need to add the --ro option and make sure LIBGUESTFS_BACKEND=direct.

> Can you post your command?

Sure, I'm using the attached test script.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)

[-- Attachment #2: test.sh --]
[-- Type: application/x-sh, Size: 771 bytes --]

  reply	other threads:[~2013-05-27 11:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  5:36 [Qemu-devel] [PATCH v6 00/12] curl: fix curl read Fam Zheng
2013-05-24  5:36 ` [Qemu-devel] [PATCH v6 01/12] curl: introduce CURLSockInfo to BDRVCURLState Fam Zheng
2013-05-24  5:36 ` [Qemu-devel] [PATCH v6 02/12] curl: change magic number to sizeof Fam Zheng
2013-05-24  5:36 ` [Qemu-devel] [PATCH v6 03/12] curl: change curl_multi_do to curl_fd_handler Fam Zheng
2013-05-24  5:36 ` [Qemu-devel] [PATCH v6 04/12] curl: fix curl_open Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 05/12] curl: add timer to BDRVCURLState Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 06/12] curl: introduce CURLDataCache Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 07/12] curl: make use of CURLDataCache Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 08/12] curl: use list to store CURLState Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 09/12] curl: add cache quota Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 10/12] curl: introduce ssl_no_cert runtime option Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 11/12] block/curl.c: Refuse to open the handle for writes Fam Zheng
2013-05-24  5:37 ` [Qemu-devel] [PATCH v6 12/12] curl: set s->url to NULL after free Fam Zheng
2013-05-24  8:07 ` [Qemu-devel] [PATCH v6 00/12] curl: fix curl read Richard W.M. Jones
2013-05-27  2:25   ` Fam Zheng
2013-05-27 11:57     ` Richard W.M. Jones [this message]
2013-05-28  7:30       ` Fam Zheng
2013-05-28  7:47         ` Richard W.M. Jones
2013-05-28  8:46           ` Richard W.M. Jones
2013-05-28  8:52             ` Fam Zheng
2013-05-28  8:53             ` Richard W.M. Jones
2013-05-28 10:35 ` Richard W.M. Jones
2013-05-28 11:01   ` Richard W.M. Jones
2013-05-28 11:14     ` Fam Zheng
2013-05-28 11:25       ` Richard W.M. Jones
2013-05-28 11:32         ` Richard W.M. Jones
2013-05-29  1:07           ` Fam Zheng
2013-05-29  9:25             ` Richard W.M. Jones
2013-05-28 11:34     ` Stefan Hajnoczi

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=20130527115720.GW4515@redhat.com \
    --to=rjones@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@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).