From: Gonglei <arei.gonglei@huawei.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: kwolf@redhat.com, lersek@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 repost 2] block/curl: Improve type safety of s->timeout.
Date: Sun, 26 Oct 2014 16:57:46 +0800 [thread overview]
Message-ID: <544CB78A.3090403@huawei.com> (raw)
In-Reply-To: <1414312958-21967-2-git-send-email-rjones@redhat.com>
On 2014/10/26 16:42, 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>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> ---
> block/curl.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index b4157cc..2b40802 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) {
why 100000? And it's a magic number.
Best regards,
-Gonglei
> + 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);
>
next prev parent reply other threads:[~2014-10-26 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 8:42 [Qemu-devel] [PATCH v1 repost 2] block/curl: Improve type safety of s->timeout Richard W.M. Jones
2014-10-26 8:42 ` Richard W.M. Jones
2014-10-26 8:57 ` Gonglei [this message]
2014-10-26 10:22 ` Richard W.M. Jones
2014-10-26 10:45 ` Gonglei
2014-10-26 10:48 ` Richard W.M. Jones
2014-10-26 10:55 ` Gonglei
2014-10-26 10:57 ` Richard W.M. Jones
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=544CB78A.3090403@huawei.com \
--to=arei.gonglei@huawei.com \
--cc=kwolf@redhat.com \
--cc=lersek@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).