mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] add support for POSIX_SPAWN_SETSID
Date: Fri, 31 Mar 2017 12:01:56 -0400	[thread overview]
Message-ID: <20170331160156.GL17319@brightrain.aerifal.cx> (raw)
In-Reply-To: <20170331050243.4485-1-quae@daurnimator.com>

On Fri, Mar 31, 2017 at 04:02:43PM +1100, daurnimator wrote:
> This patch adds support for the POSIX_SPAWN_SETSID flag.
> 
> It was recently accepted by the Austin Group:
> http://austingroupbugs.net/view.php?id=1044
> 
> ---
>  include/spawn.h           | 1 +
>  src/process/posix_spawn.c | 4 ++++
>  2 files changed, 5 insertions(+)
> 
> diff --git a/include/spawn.h b/include/spawn.h
> index 29c799ee..7dee7cfa 100644
> --- a/include/spawn.h
> +++ b/include/spawn.h
> @@ -21,6 +21,7 @@ struct sched_param;
>  #define POSIX_SPAWN_SETSIGMASK 8
>  #define POSIX_SPAWN_SETSCHEDPARAM 16
>  #define POSIX_SPAWN_SETSCHEDULER 32
> +#define POSIX_SPAWN_SETSID 64

This overlaps with the glibc value for POSIX_SPAWN_USEVFORK; while we
don't implement it, we also don't want to have mismatched constant
ABI.

I know this is asking a lot, but could you possibly submit a glibc
patch too so the intended value (128 I guess?) is established on their
side too, or (yay if you can!) poke somebody else to do it? In the
past I've tried to just get them to casually agree to assigning values
for things like this before they implement them, but I haven't had
much luck.

Cc'ing libc-alpha too.

Rich


  reply	other threads:[~2017-03-31 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-31  5:02 daurnimator
2017-03-31 16:01 ` Rich Felker [this message]
2017-04-22 23:19   ` Rich Felker
2017-04-22 23:43     ` [musl] " Zack Weinberg
2017-04-22 23:47       ` Rich Felker
2017-04-22 23:49         ` [musl] " Zack Weinberg

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=20170331160156.GL17319@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=libc-alpha@sourceware.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).