public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: Document the fexecve function
Date: Tue, 28 Apr 2020 19:25:13 +0200	[thread overview]
Message-ID: <877dxzo746.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <871ro9z2rv.fsf@mid.deneb.enyo.de> (Florian Weimer's message of "Mon, 27 Apr 2020 11:39:00 +0200")

* Florian Weimer:

> -----
>  manual/process.texi | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/manual/process.texi b/manual/process.texi
> index 5728bde2cb..b20ad26cbf 100644
> --- a/manual/process.texi
> +++ b/manual/process.texi
> @@ -405,6 +405,19 @@ be an array of strings in the same format as for the @code{environ}
>  variable; see @ref{Environment Access}.
>  @end deftypefun
>  
> +@deftypefun int fexecve (int @var{fd},  char *const @var{argv}@t{[]}, char *const @var{env}@t{[]})
> +@standards{POSIX.1, unistd.h}
> +@safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
> +This is similar to @code{execve}, but instead identifying the progam
> +executable by its pathname, the file descriptor @var{fd} is used.  The
> +descriptor must have been opened with the @code{O_RDONLY} flag or (on
> +Linux) the @code{O_PATH} flag.
> +
> +On Linux, @code{fexecve} can fail with an error of @code{ENOSYS} if
> +@file{/proc} has not been mounted and the kernel lacks support for the
> +underlying @code{execveat} system call.
> +@end deftypefun
> +
>  @deftypefun int execle (const char *@var{filename}, const char *@var{arg0}, @dots{}, char *const @var{env}@t{[]})
>  @standards{POSIX.1, unistd.h}
>  @safety{@prelim{}@mtsafe{}@asunsafe{@ascuheap{}}@acunsafe{@acsmem{}}}

I pushed this by accident, but Joseph has reviewed the patch here:

  <https://sourceware.org/pipermail/libc-alpha/2020-April/113290.html>


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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  9:39 Florian Weimer
2020-04-28 17:25 ` Florian Weimer [this message]
2020-04-29  6:00 ` Michael Kerrisk
2020-04-29  8:16   ` Florian Weimer

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=877dxzo746.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --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).