From: "Richard W.M. Jones" <rjones@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-trivial@nongnu.org, kwolf@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] curl: Don't set curl options on the handle just before it's going to be deleted.
Date: Mon, 10 Jun 2013 17:35:50 +0100 [thread overview]
Message-ID: <20130610163550.GD4515@redhat.com> (raw)
In-Reply-To: <51B5F21C.9020700@msgid.tls.msk.ru>
On Mon, Jun 10, 2013 at 07:34:52PM +0400, Michael Tokarev wrote:
> 10.06.2013 17:19, Richard W.M. Jones wrote:
> > From: "Richard W.M. Jones" <rjones@redhat.com>
> >
> > (Found by Kamil Dudka)
> >
> > Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
> > ---
> > block/curl.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/block/curl.c b/block/curl.c
> > index b634ccf..bf31efe 100644
> > --- a/block/curl.c
> > +++ b/block/curl.c
> > @@ -453,7 +453,6 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags)
> > goto out;
> > curl_easy_getinfo(state->curl, CURLINFO_CONTENT_LENGTH_DOWNLOAD, &d);
> > curl_easy_setopt(state->curl, CURLOPT_WRITEFUNCTION, (void *)curl_read_cb);
> > - curl_easy_setopt(state->curl, CURLOPT_NOBODY, 0);
> > if (d)
> > s->len = (size_t)d;
> > else if(!s->len)
>
> Adding a bit more context:
>
>
> curl_easy_setopt(state->curl, CURLOPT_NOBODY, 1);
> curl_easy_setopt(state->curl, CURLOPT_WRITEFUNCTION, (void *)curl_size_cb);
> if (curl_easy_perform(state->curl))
> goto out;
> curl_easy_getinfo(state->curl, CURLINFO_CONTENT_LENGTH_DOWNLOAD, &d);
> curl_easy_setopt(state->curl, CURLOPT_WRITEFUNCTION, (void *)curl_read_cb);
> =>> curl_easy_setopt(state->curl, CURLOPT_NOBODY, 0);
> if (d)
> s->len = (size_t)d;
> else if(!s->len)
> goto out;
> DPRINTF("CURL: Size = %zd\n", s->len);
>
> curl_clean_state(state);
> curl_easy_cleanup(state->curl);
> state->curl = NULL;
>
> So indeed, the curl object is being removed here a few lines down the code.
>
> But it looks like the previous call to curl_easy_setopt, to set WRITEFUNCTION,
> is also not very useful. Should we probably want to remove that too, or don't
> remove either of these?
Yes you're right. For some reason I "saw" another call to
curl_easy_perform which obviously isn't there in reality. Will send a
v2 patch shortly after I've done a bit of testing.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
prev parent reply other threads:[~2013-06-10 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 13:19 [Qemu-devel] [PATCH] curl: Don't set curl options on the handle just before it's going to be deleted Richard W.M. Jones
2013-06-10 15:34 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
2013-06-10 16:35 ` Richard W.M. Jones [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=20130610163550.GD4515@redhat.com \
--to=rjones@redhat.com \
--cc=kwolf@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).