From: Eric Blake <eblake@redhat.com>
To: P J P <ppandit@redhat.com>, Qemu Developers <qemu-devel@nongnu.org>
Cc: Riku Voipio <riku.voipio@iki.fi>, Jann Horn <jannh@google.com>,
Peter Maydell <peter.maydell@linaro.org>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] linux-user: allocate heap memory for execve arguments
Date: Mon, 6 Mar 2017 09:53:46 -0600 [thread overview]
Message-ID: <988a673c-01cd-0c1e-133c-22e299653502@redhat.com> (raw)
In-Reply-To: <20170306071721.26708-3-ppandit@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
On 03/06/2017 01:17 AM, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> Arguments passed to execve(2) call from user program could
> be large, allocating stack memory for them via alloca(3) call
> would lead to bad behaviour. Use 'g_malloc0' to allocate memory
> for such arguments.
>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
> linux-user/syscall.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
Is this patch alone (without 1/2) sufficient to solve the problem? If
so, then drop 1/2.
>
> Update per: replace alloca() with g_malloc0()
> -> https://lists.gnu.org/archive/html/qemu-devel/2017-03/msg00750.html
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 86a4a9c..404fb0b 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -7800,8 +7800,8 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
What version of qemu are you patching? Line 7800 of current master is
nowhere near 'case TARGET_NR_execve:' (line 7899)
> ret = -TARGET_E2BIG;
> break;
> }
and current master has 'goto efault' rather than directly setting ret at
this point.
> - argp = alloca((argc + 1) * sizeof(void *));
> - envp = alloca((envc + 1) * sizeof(void *));
> + argp = g_malloc0((argc + 1) * sizeof(void *));
> + envp = g_malloc0((envc + 1) * sizeof(void *));
Subject to a potential multiplication overflow. I'd prefer:
g_new0(void *, argc + 1);
as that is guaranteed to not overflow.
>
> for (gp = guest_argp, q = argp; gp;
> gp += sizeof(abi_ulong), q++) {
> @@ -7862,6 +7862,9 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
> break;
> unlock_user(*q, addr, 0);
> }
> +
> + g_free(argp);
> + g_free(envp);
> }
> break;
> case TARGET_NR_chdir:
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-03-06 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 7:17 [Qemu-devel] [PATCH v2 0/2] Limit and protect execve arguments P J P
2017-03-06 7:17 ` [Qemu-devel] [PATCH v2 1/2] linux-user: limit number of arguments to execve P J P
2017-03-06 15:42 ` Peter Maydell
2017-03-06 15:54 ` Eric Blake
2017-03-06 7:17 ` [Qemu-devel] [PATCH v2 2/2] linux-user: allocate heap memory for execve arguments P J P
2017-03-06 15:53 ` Eric Blake [this message]
2017-03-06 16:08 ` Eric Blake
2017-03-06 18:06 ` P J P
2017-03-06 18:11 ` Eric Blake
2017-03-06 18:43 ` P J P
2017-03-06 15:57 ` Peter Maydell
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=988a673c-01cd-0c1e-133c-22e299653502@redhat.com \
--to=eblake@redhat.com \
--cc=jannh@google.com \
--cc=peter.maydell@linaro.org \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).