All of lore.kernel.org
 help / color / mirror / Atom feed
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 17:07:48 +0100	[thread overview]
Message-ID: <20020214170748.B17490@outpost.ds9a.nl> (raw)
In-Reply-To: <20020214165143.A16601@outpost.ds9a.nl> <38300000.1013702447@baldur>
In-Reply-To: <38300000.1013702447@baldur>; from dmccr@us.ibm.com on Thu, Feb 14, 2002 at 04:03:47PM +0000

On Thu, Feb 14, 2002 at 04:03:47PM +0000, Dave McCracken wrote:

> It's the expected behavior for a task-based model like Linux.  Each task is
> independent and inherits the uid/gid from whoever called clone().  It's
> just one of several resources that are specified as process-wide in POSIX,
> but are per-task in Linux.

Could this also be solved by making threads call 'clone' themselves? 

> I've been working on a patch to allow clone() to specify shared
> credentials, but it's been on the back burner.

Would be much appreciated.

Regards,

bert hubert

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

  reply	other threads:[~2002-02-14 16:08 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 [this message]
2002-02-14 16:19     ` Dave McCracken
2002-02-14 17:05       ` bert hubert
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=20020214170748.B17490@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.