All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Subject: Re: linux-user: keep the name-ending parenthesis in /proc/self/stat
Date: Thu, 09 Apr 2020 16:27:47 +0100	[thread overview]
Message-ID: <87wo6oadcc.fsf@linaro.org> (raw)
In-Reply-To: <fb4c55fa-d539-67ee-c6c9-de8fb63c8488@inria.fr>


Brice Goglin <Brice.Goglin@inria.fr> writes:

> When the program name is very long, qemu-user may truncate it in
> /proc/self/stat. However the truncation must keep the ending ") "
> to conform to the proc manpage which says:
>     (2) comm  %s
>            The  filename of the executable, in parentheses.  This
>            is visible whether or not the  executable  is  swapped
>            out.
>
> To reproduce:
> $ ln -s /bin/cat <filenamewithmorethan128chars>
> $ qemu-x86_64 ./<filenamewithmorethan128chars> /proc/self/stat
>
> Before the patch, you get:
> 1134631 (<filenametruncated>0 0 0 0 0 0 0 0 ...
> After the patch:
> 1134631 (<filenametruncat>) 0 0 0 0 0 0 0 0 ...
>
> This fixes an issue with hwloc failing to parse /proc/self/stat
> when Ludovic Courtes was testing it in Guix over qemu-aarch64.
>
> Signed-off-by: Philippe_Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Brice Goglin <Brice.Goglin@inria.fr>
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -7305,7 +7305,11 @@ static int open_self_stat(void *cpu_env, int fd)
>          snprintf(buf, sizeof(buf), "%"PRId64 " ", val);
>        } else if (i == 1) {
>          /* app name */
> -        snprintf(buf, sizeof(buf), "(%s) ", ts->bprm->argv[0]);
> +        char *ptr = buf;
> +
> +        *ptr++ = '(';
> +        ptr = stpncpy(ptr, ts->bprm->argv[0], sizeof(buf) - 3);
> +        strcpy(ptr, ") ");

why not just use a format string:

  snprintf(buf, sizeof(buf), "(%.125s) ", ts->bprm->argv[0]);

although to be honest when ever I see a bunch of sizeof(buf) code for
strings I tend to re-write it to use the glib GString functions.

>        } else if (i == 27) {
>          /* stack bottom */
>          val = start_stack;


-- 
Alex Bennée


  parent reply	other threads:[~2020-04-09 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08  8:24 linux-user: keep the name-ending parenthesis in /proc/self/stat Brice Goglin
2020-04-08 15:48 ` Laurent Vivier
2020-04-08 15:56   ` Brice Goglin
2020-04-09 15:27 ` Alex Bennée [this message]
2020-04-09 15:34   ` Brice Goglin
2020-04-09 19:59     ` Alex Bennée
  -- strict thread matches above, loose matches on Subject: below --
2020-03-30 19:07 Brice Goglin
2020-03-30 22:05 ` Philippe Mathieu-Daudé
2020-03-30 22:29   ` Brice Goglin
2020-04-08  6:40     ` Brice Goglin
2020-04-08  8:09       ` Laurent Vivier

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=87wo6oadcc.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=Brice.Goglin@inria.fr \
    --cc=philmd@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 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.