From: Laurent Vivier <laurent@vivier.eu>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user/elfload: fix filling psinfo->pr_psargs
Date: Sat, 15 May 2021 21:59:31 +0200 [thread overview]
Message-ID: <aa2dee61-91b3-7d7c-9fce-774f65857523@vivier.eu> (raw)
In-Reply-To: <20210413205814.22821-1-iii@linux.ibm.com>
Le 13/04/2021 à 22:58, Ilya Leoshkevich a écrit :
> The current code dumps the memory between arg_start and arg_end,
> which contains the argv pointers. This results in the
>
> Core was generated by `<garbage>`
>
> message when opening the core file in GDB. This is because the code is
> supposed to dump the actual arg strings. Fix by using arg_strings and
> env_strings instead of arg_start and arg_end.
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> linux-user/elfload.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/linux-user/elfload.c b/linux-user/elfload.c
> index 4e45bd1539..cffcebfe45 100644
> --- a/linux-user/elfload.c
> +++ b/linux-user/elfload.c
> @@ -3662,10 +3662,10 @@ static int fill_psinfo(struct target_elf_prpsinfo *psinfo, const TaskState *ts)
>
> (void) memset(psinfo, 0, sizeof (*psinfo));
>
> - len = ts->info->arg_end - ts->info->arg_start;
> + len = ts->info->env_strings - ts->info->arg_strings;
> if (len >= ELF_PRARGSZ)
> len = ELF_PRARGSZ - 1;
> - if (copy_from_user(&psinfo->pr_psargs, ts->info->arg_start, len))
> + if (copy_from_user(&psinfo->pr_psargs, ts->info->arg_strings, len))
> return -EFAULT;
> for (i = 0; i < len; i++)
> if (psinfo->pr_psargs[i] == 0)
>
Applied to my linux-user-for-6.1 branch.
Thanks,
Laurent
prev parent reply other threads:[~2021-05-15 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 20:58 [PATCH] linux-user/elfload: fix filling psinfo->pr_psargs Ilya Leoshkevich
2021-04-13 21:03 ` no-reply
2021-05-15 19:59 ` Laurent Vivier [this message]
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=aa2dee61-91b3-7d7c-9fce-774f65857523@vivier.eu \
--to=laurent@vivier.eu \
--cc=borntraeger@de.ibm.com \
--cc=iii@linux.ibm.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).