public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] Linux: Add execveat system call wrapper
Date: Tue, 28 Apr 2020 14:44:11 -0300	[thread overview]
Message-ID: <c9a29aa3-6010-8206-6219-b01c238a9608@linaro.org> (raw)
In-Reply-To: <20200428122019.26826-1-ahajkova@redhat.com>



On 28/04/2020 09:20, Alexandra Hájková via Libc-alpha wrote:

> +/* Execute the file FD refers to, overlaying the running program image.
> +   ARGV and ENVP are passed to the new program, as for `execve'.  */
> +int
> +execveat (int dirfd, const char *path, char *const argv[], char *const envp[],
> +          int flags)
> +{
> +  /* Avoid implicit array coercion in syscall macros.  */
> +  INLINE_SYSCALL_CALL (execveat, dirfd, path, &argv[0], &envp[0], flags);
> +#ifndef __ASSUME_EXECVEAT
> +  if (errno != ENOSYS)
> +    return -1;
> +
> +  int fd = openat (dirfd, path, flags | O_CLOEXEC);
> +  if (fd < 0)
> +    return -1;
> +

Is this subject to a TOCTOU where a thread might close the fd by explicitly
reading /proc/self/fd/?


> +  struct fd_to_filename fdfilename;
> +  const char *gfilename
> +    = path != NULL ? path : __fd_to_filename (fd, &fdfilename);
> +> +  /* We do not need the return value.  */
> +  __	execve (gfilename, argv, envp);
> +
> +  int save = errno;
> +
> +  /* We come here only if the 'execve' call fails.  Determine whether
> +     /proc is mounted.  If not we return ENOSYS.  */
> +  struct stat st;
> +  if (stat ("/proc/self/fd", &st) != 0 && errno == ENOENT)
> +    save = ENOSYS;
> +
> +  close (fd);
> +  __set_errno (save);
> +#endif
> +
> +  return -1;
> +}



  parent reply	other threads:[~2020-04-28 17:44 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 12:20 Alexandra Hájková
2020-04-28 14:17 ` Florian Weimer
2020-04-28 15:03   ` Joseph Myers
2020-04-28 15:03 ` Joseph Myers
2020-04-28 15:08   ` Florian Weimer
2020-04-28 15:29     ` Joseph Myers
2020-04-28 17:15       ` Florian Weimer
2020-04-28 17:19         ` Joseph Myers
2020-04-28 17:44 ` Adhemerval Zanella [this message]
2020-04-28 17:50   ` Florian Weimer
2020-04-28 18:31     ` Adhemerval Zanella
2020-04-30 11:15 ` Florian Weimer
2020-04-30 12:28   ` Adhemerval Zanella
2020-04-30 12:55     ` Florian Weimer
2020-04-30 19:03       ` Adhemerval Zanella
2020-04-30 12:32 ` Adhemerval Zanella
2020-11-06 21:03 ` Alexandra Hájková
2020-11-06 22:15   ` Joseph Myers
2020-11-09 18:43     ` Florian Weimer
2020-11-09 21:34   ` Yann Droneaud
2020-11-26 11:31     ` Alexandra Petlanova Hajkova
2020-11-09 20:39 ` Adhemerval Zanella
2020-12-03 13:55   ` Florian Weimer
2020-11-26 21:28 ` Alexandra Hájková
2020-11-27 14:58   ` Adhemerval Zanella
2020-11-27 17:32     ` Florian Weimer
2020-11-27 17:38       ` Adhemerval Zanella
2020-12-03 14:20 ` Alexandra Hájková
2020-12-03 14:37   ` Andreas Schwab
2020-12-08 14:44   ` Adhemerval Zanella
2020-12-08 15:18     ` Florian Weimer
2020-12-08 16:41       ` Adhemerval Zanella
2021-03-15 21:42 ` Alexandra Hájková
2021-03-15 22:12   ` Joseph Myers
2021-03-15 22:17   ` Dmitry V. Levin
2021-03-24 13:54 ` Alexandra Hájková
2021-03-26 20:36   ` Adhemerval Zanella
2021-04-02 12:13     ` Alexandra Hájková
2021-04-02 13:29       ` Adhemerval Zanella
2021-04-05 16:32 ` Alexandra Hájková
2021-04-12 10:26   ` Alexandra Hájková
2021-04-12 11:14   ` Andreas Schwab
2021-04-12 19:26 ` Alexandra Hájková
2021-04-13 19:27   ` Adhemerval Zanella
2021-04-21 18:11 ` Alexandra Hájková
2021-05-03 19:20   ` Adhemerval Zanella

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=c9a29aa3-6010-8206-6219-b01c238a9608@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).