From: "Daniel P. Berrangé" <berrange@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
QEMU Developers <qemu-devel@nongnu.org>,
niuguoxiang <niuguoxiang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] qga: check length of command-line & environment variables
Date: Fri, 11 Jan 2019 09:56:54 +0000 [thread overview]
Message-ID: <20190111095654.GH18491@redhat.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1901111453590.12783@xnncv>
On Fri, Jan 11, 2019 at 03:22:51PM +0530, P J P wrote:
> +-- On Mon, 7 Jan 2019, P J P wrote --+
> | Qemu guest agent while executing user commands does not seem to
> | check length of argument list and/or environment variables passed.
> | It may lead to integer overflow or infinite loop issues. Add check
> | to avoid it.
> |
> | - size_t str_size = 1;
> | + size_t str_size = 1, args_max;
> |
> | + args_max = sysconf(_SC_ARG_MAX);
>
> Looks like sysconf()/_SC_ARG_MAX declarations aren't available. Is it okay to
> include header <unistd.h> ?
qga/commands.c already includes qemu/osdep.h which includs unistd.h.
The build problem patchew reported was from *mingw* builds where
sysconf does not exist.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-01-11 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 10:34 [Qemu-devel] [PATCH] qga: check length of command-line & environment variables P J P
2019-01-07 13:04 ` no-reply
2019-01-11 9:52 ` P J P
2019-01-11 9:56 ` Daniel P. Berrangé [this message]
2019-01-13 17:28 ` P J P
2019-01-22 3:49 ` [Qemu-devel] 答复: " niuguoxiang
2019-01-24 17:38 ` [Qemu-devel] " Michael Roth
2019-01-24 17:53 ` P J P
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=20190111095654.GH18491@redhat.com \
--to=berrange@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=niuguoxiang@huawei.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).