From: bert hubert <ahu@ds9a.nl>
To: Dave McCracken <dmccr@us.ibm.com>
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 18:05:07 +0100 [thread overview]
Message-ID: <20020214180507.A18665@outpost.ds9a.nl> (raw)
In-Reply-To: <20020214165143.A16601@outpost.ds9a.nl> <38300000.1013702447@baldur> <20020214170748.B17490@outpost.ds9a.nl> <46860000.1013703583@baldur>
In-Reply-To: <46860000.1013703583@baldur>; from dmccr@us.ibm.com on Thu, Feb 14, 2002 at 04:21:52PM +0000
On Thu, Feb 14, 2002 at 04:21:52PM +0000, Dave McCracken wrote:
> The only workaround I can think of is, as you discovered, to do the
> setuid() call before you create any threads, and thus create underlying
> kernel tasks. Once the kernel tasks have been created each one has its own
> credentials and has to be changed separately.
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.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
Netherlabs BV / Rent-a-Nerd.nl - Nerd Available -
Linux Advanced Routing & Traffic Control: http://ds9a.nl/lartc
next prev parent reply other threads:[~2002-02-14 17:05 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 [this message]
2002-02-14 17:14 ` Dave McCracken
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=20020214180507.A18665@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=dmccr@us.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.