public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: posix_spawn issues on i686
Date: Wed, 12 Jan 2022 11:41:43 +0100	[thread overview]
Message-ID: <Yd6wZ0r7EXOGcQfQ@calimero.vinschen.de> (raw)
In-Reply-To: <0a091366-a949-d7d0-6ad1-030ddd11c7dc@cornell.edu>

On Jan 11 16:08, Ken Brown wrote:
> On 1/11/2022 1:45 PM, Jeremy Drake via Cygwin wrote:
> > Sorry, I am not subscribed to the list so don't have the message to reply
> > to for threading purposes, but attached please find a C reproducer that
> > works on x86_64 but fails on i686.  The particular issue seems to be the
> > POSIX_SPAWN_RESETIDS flag - not setting that allows i686 to succeed too.

Thanks for the STC, Jeremy!

> I don't have time to check this carefully, but it looks to me like the
> problem is that process_spawnattr calls setegid and seteuid instead of
> setegid32 and seteuid32.  This causes truncation of the gid and uid.

You're right.  Additionally the calls to getgid and getuid have to use
the internal getgid32 and getuid32 functions.

I'll apply a fix.


Thanks guys!
Corinna

  reply	other threads:[~2022-01-12 10:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 19:38 Jeremy Drake
2022-01-11 10:07 ` Corinna Vinschen
2022-01-11 18:45 ` Jeremy Drake
2022-01-11 21:08   ` Ken Brown
2022-01-12 10:41     ` Corinna Vinschen [this message]
2022-01-12 11:24       ` Corinna Vinschen
2022-01-12 16:32       ` Ken Brown
2022-01-12 21:25     ` Jeremy Drake
2022-01-14  9:15       ` Corinna Vinschen

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=Yd6wZ0r7EXOGcQfQ@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).