From: Dave McCracken <dmccr@us.ibm.com>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-kernel@vger.kernel.org, drepper@redhat.com, torvalds@transmeta.com
Subject: Re: setuid/pthread interaction broken? 'clone_with_uid()?'
Date: Thu, 14 Feb 2002 11:14:24 -0600 [thread overview]
Message-ID: <66390000.1013706864@baldur> (raw)
In-Reply-To: <20020214180507.A18665@outpost.ds9a.nl>
In-Reply-To: <20020214165143.A16601@outpost.ds9a.nl> <38300000.1013702447@baldur> <20020214170748.B17490@outpost.ds9a.nl> <46860000.1013703583@baldur> <20020214180507.A18665@outpost.ds9a.nl>
--On Thursday, February 14, 2002 18:05:07 +0100 bert hubert <ahu@ds9a.nl>
wrote:
> I'm wondering what the right semantics are. POSIX is one thing, but having
> the ability to have threads with different uids in one VM would have its
> uses too.
That's the idea behind the patch I've been working on. It would be an
option to clone(), just like sharing address space, signals, and files.
The pthread libraries could turn it on for POSIX behavior, and programs
that wanted something different could call clone() with their own flags.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
prev parent reply other threads:[~2002-02-14 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 15:51 setuid/pthread interaction broken? 'clone_with_uid()?' bert hubert
2002-02-14 16:00 ` Dave McCracken
2002-02-14 16:07 ` bert hubert
2002-02-14 16:19 ` Dave McCracken
2002-02-14 17:05 ` bert hubert
2002-02-14 17:14 ` Dave McCracken [this message]
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=66390000.1013706864@baldur \
--to=dmccr@us.ibm.com \
--cc=ahu@ds9a.nl \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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