From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: fix warning for source_return_path_thread
Date: Wed, 9 Mar 2016 08:54:51 +0100 [thread overview]
Message-ID: <56DFD6CB.90906@redhat.com> (raw)
In-Reply-To: <1457503932-31763-1-git-send-email-peterx@redhat.com>
On 09/03/2016 07:12, Peter Xu wrote:
> max_len is not necessary, while it brings a warning during compilation
> when specify "-Wstack-usage=1000000". Replacing using sizeof().
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> migration/migration.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 0129d9f..6680d95 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -1268,8 +1268,7 @@ static void *source_return_path_thread(void *opaque)
> MigrationState *ms = opaque;
> QEMUFile *rp = ms->rp_state.from_dst_file;
> uint16_t header_len, header_type;
> - const int max_len = 512;
> - uint8_t buf[max_len];
> + uint8_t buf[512];
> uint32_t tmp32, sibling_error;
> ram_addr_t start = 0; /* =0 to silence warning */
> size_t len = 0, expected_len;
> @@ -1292,7 +1291,7 @@ static void *source_return_path_thread(void *opaque)
>
> if ((rp_cmd_args[header_type].len != -1 &&
> header_len != rp_cmd_args[header_type].len) ||
> - header_len > max_len) {
> + header_len > sizeof(buf)) {
sizeof works fine because buf is an array of bytes, but ARRAY_SIZE is
better because it works for any type of buffer.
Paolo
> error_report("RP: Received '%s' message (0x%04x) with"
> "incorrect length %d expecting %zu",
> rp_cmd_args[header_type].name, header_type, header_len,
>
next prev parent reply other threads:[~2016-03-09 7:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 6:12 [Qemu-devel] [PATCH] migration: fix warning for source_return_path_thread Peter Xu
2016-03-09 7:54 ` Paolo Bonzini [this message]
2016-03-09 8:26 ` Peter Xu
2016-03-09 9:30 ` Paolo Bonzini
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=56DFD6CB.90906@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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.