From: Peter Samuelson <peter@cadcamlab.org>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] new setprocuid syscall
Date: Tue, 20 Feb 2001 07:00:41 -0600 [thread overview]
Message-ID: <20010220070041.A12011@cadcamlab.org> (raw)
In-Reply-To: <Pine.A41.4.31.0102192312330.174604-100000@pandora.inf.elte.hu> <20010219230106.A23699@cadcamlab.org> <3A924CA1.10C913E7@evision-ventures.com>
In-Reply-To: <3A924CA1.10C913E7@evision-ventures.com>; from dalecki@evision-ventures.com on Tue, Feb 20, 2001 at 11:53:21AM +0100
[Peter Samuelson]
> > Race -- you need to make sure the task_struct doesn't disappear out
> > from under you.
> >
> > Anyway, why not use the interface 'chown uid /proc/pid'? No new
> > syscall, no arch-dependent part, no user-space tool, etc.
[Martin Dalecki]
> Becouse of exactly the same race condition as above maybe?
OK then, what is the right way to make sure a task doesn't disappear?
I assumed 'read_lock (&tasklist_lock)' was enough, from reading other
code.
Peter
next prev parent reply other threads:[~2001-02-20 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-19 22:18 BERECZ Szabolcs
2001-02-20 5:01 ` Peter Samuelson
2001-02-20 10:53 ` Martin Dalecki
2001-02-20 13:00 ` Peter Samuelson [this message]
2001-02-20 11:42 ` Alan Cox
2001-02-20 13:11 ` Peter Samuelson
2001-02-20 13:52 ` Alan Cox
2001-02-20 17:04 ` BERECZ Szabolcs
2000-01-01 0:28 ` Pavel Machek
2001-02-21 4:19 ` Peter Samuelson
2001-02-20 12:14 ` BERECZ Szabolcs
2001-02-20 12:52 ` Peter Samuelson
2001-02-20 12:02 ` Philipp Rumpf
2001-02-20 14:19 Petr Vandrovec
2001-02-23 17:13 Bernd Jendrissek
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=20010220070041.A12011@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®