qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Lirong Yuan <yuanzi@google.com>,
	qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [PATCH] linux-user: Add AT_EXECFN and AT_EXECFD auxval
Date: Mon, 2 Mar 2020 15:38:56 +0100	[thread overview]
Message-ID: <f9ef0046-9d0f-c53d-bf58-417df31705a6@vivier.eu> (raw)
In-Reply-To: <20200221202857.126170-1-yuanzi@google.com>

Le 21/02/2020 à 21:28, Lirong Yuan a écrit :
> This change adds the support for AT_EXECFN and AT_EXECFD auxval.

Why do we need AT_EXECFD?

AT_EXECFD is normally only used with binfmt_misc so I don't see any use
cases for it with QEMU.

For AT_EXECFN, according to kernel commit

  651910874633 execve filename: document and export via auxiliary vector

It sould be like readlink("/proc/self/exe",), and thus I think we should
use realpath() like we have in syscall.c for TARGET_NR_readlink:

 8843     case TARGET_NR_readlink:
...
 8854                 char real[PATH_MAX], *temp;
 8855                 temp = realpath(exec_path, real);
...

Thanks,
Laurent

> 
> Signed-off-by: Lirong Yuan <yuanzi@google.com>
> ---
>  linux-user/elfload.c | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/linux-user/elfload.c b/linux-user/elfload.c
> index f3080a1635..7e0f3042f1 100644
> --- a/linux-user/elfload.c
> +++ b/linux-user/elfload.c
> @@ -1568,7 +1568,7 @@ struct exec
>                                   ~(abi_ulong)(TARGET_ELF_EXEC_PAGESIZE-1))
>  #define TARGET_ELF_PAGEOFFSET(_v) ((_v) & (TARGET_ELF_EXEC_PAGESIZE-1))
>  
> -#define DLINFO_ITEMS 15
> +#define DLINFO_ITEMS 17
>  
>  static inline void memcpy_fromfs(void * to, const void * from, unsigned long n)
>  {
> @@ -1888,11 +1888,14 @@ static abi_ulong loader_build_fdpic_loadmap(struct image_info *info, abi_ulong s
>      return sp;
>  }
>  
> -static abi_ulong create_elf_tables(abi_ulong p, int argc, int envc,
> +static abi_ulong create_elf_tables(struct linux_binprm *bprm,
>                                     struct elfhdr *exec,
>                                     struct image_info *info,
>                                     struct image_info *interp_info)
>  {
> +    abi_ulong p = bprm->p;
> +    int argc = bprm->argc;
> +    int envc = bprm->envc;
>      abi_ulong sp;
>      abi_ulong u_argc, u_argv, u_envp, u_auxv;
>      int size;
> @@ -2032,6 +2035,8 @@ static abi_ulong create_elf_tables(abi_ulong p, int argc, int envc,
>      NEW_AUX_ENT(AT_CLKTCK, (abi_ulong) sysconf(_SC_CLK_TCK));
>      NEW_AUX_ENT(AT_RANDOM, (abi_ulong) u_rand_bytes);
>      NEW_AUX_ENT(AT_SECURE, (abi_ulong) qemu_getauxval(AT_SECURE));
> +    NEW_AUX_ENT(AT_EXECFN, info->file_string);
> +    NEW_AUX_ENT(AT_EXECFD, bprm->fd);
>  
>  #ifdef ELF_HWCAP2
>      NEW_AUX_ENT(AT_HWCAP2, (abi_ulong) ELF_HWCAP2);
> @@ -2870,8 +2875,8 @@ int load_elf_binary(struct linux_binprm *bprm, struct image_info *info)
>  #endif
>      }
>  
> -    bprm->p = create_elf_tables(bprm->p, bprm->argc, bprm->envc, &elf_ex,
> -                                info, (elf_interpreter ? &interp_info : NULL));
> +    bprm->p = create_elf_tables(bprm, &elf_ex, info,
> +                                (elf_interpreter ? &interp_info : NULL));
>      info->start_stack = bprm->p;
>  
>      /* If we have an interpreter, set that as the program's entry point.
> 



  parent reply	other threads:[~2020-03-02 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21 20:28 [PATCH] linux-user: Add AT_EXECFN and AT_EXECFD auxval Lirong Yuan
2020-02-29  0:41 ` Lirong Yuan
2020-03-02 14:38 ` Laurent Vivier [this message]
2020-03-02 18:18   ` Lirong Yuan
2020-03-02 18:31     ` Laurent Vivier
2020-03-02 19:54       ` Lirong Yuan

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=f9ef0046-9d0f-c53d-bf58-417df31705a6@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=yuanzi@google.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 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).