From: Laszlo Ersek <lersek@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] block/curl: Improve type safety of s->timeout.
Date: Mon, 06 Oct 2014 16:38:59 +0200 [thread overview]
Message-ID: <5432A983.9040101@redhat.com> (raw)
In-Reply-To: <1412605930-3397-1-git-send-email-rjones@redhat.com>
On 10/06/14 16:32, Richard W.M. Jones wrote:
> qemu_opt_get_number returns a uint64_t, and curl_easy_setopt expects a
> long (not an int).
>
> Store the timeout (which is a positive number of seconds) as a
> uint64_t. Check that the number given by the user is reasonable.
> Cast it to long before calling curl_easy_setopt.
>
> Example error message after this change has been applied:
>
> $ ./qemu-img create -f qcow2 /tmp/test.qcow2 \
> -b 'json: { "file.driver":"https",
> "file.url":"https://foo/bar",
> "file.timeout":-1 }'
> qemu-img: /tmp/test.qcow2: Could not open 'json: { "file.driver":"https", "file.url":"https://foo/bar", "file.timeout":-1 }': timeout parameter is too large or negative: Invalid argument
>
> Signed-off-by: Richard W.M. Jones <rjones@redhat.com>
> ---
> block/curl.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index 225407c..5233ff6 100644
> --- a/block/curl.c
> +++ b/block/curl.c
> @@ -112,7 +112,7 @@ typedef struct BDRVCURLState {
> char *url;
> size_t readahead_size;
> bool sslverify;
> - int timeout;
> + uint64_t timeout;
> char *cookie;
> bool accept_range;
> AioContext *aio_context;
> @@ -390,7 +390,7 @@ static CURLState *curl_init_state(BlockDriverState *bs, BDRVCURLState *s)
> if (s->cookie) {
> curl_easy_setopt(state->curl, CURLOPT_COOKIE, s->cookie);
> }
> - curl_easy_setopt(state->curl, CURLOPT_TIMEOUT, s->timeout);
> + curl_easy_setopt(state->curl, CURLOPT_TIMEOUT, (long)s->timeout);
> curl_easy_setopt(state->curl, CURLOPT_WRITEFUNCTION,
> (void *)curl_read_cb);
> curl_easy_setopt(state->curl, CURLOPT_WRITEDATA, (void *)state);
> @@ -546,6 +546,10 @@ static int curl_open(BlockDriverState *bs, QDict *options, int flags,
>
> s->timeout = qemu_opt_get_number(opts, CURL_BLOCK_OPT_TIMEOUT,
> CURL_TIMEOUT_DEFAULT);
> + if (s->timeout > 100000) {
> + error_setg(errp, "timeout parameter is too large or negative");
> + goto out_noclean;
> + }
>
> s->sslverify = qemu_opt_get_bool(opts, CURL_BLOCK_OPT_SSLVERIFY, true);
>
>
Since we're validating s->timeout -- is a zero value okay?
Thanks
Laszlo
next prev parent reply other threads:[~2014-10-06 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 14:32 [Qemu-devel] [PATCH] block/curl: Improve type safety of s->timeout Richard W.M. Jones
2014-10-06 14:38 ` Laszlo Ersek [this message]
2014-10-06 14:40 ` Richard W.M. Jones
2014-10-06 14:43 ` Laszlo Ersek
2014-10-28 14:29 ` Stefan Hajnoczi
2014-10-29 2:08 ` Gonglei
2014-10-29 9:52 ` 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=5432A983.9040101@redhat.com \
--to=lersek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.