From: Andreas Schwab <schwab@suse.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: Todd Inglett <tinglett@vnet.ibm.com>,
Alexander Viro <viro@math.psu.edu>,
linux-kernel@vger.kernel.org
Subject: Re: SMP races in proc with thread_struct
Date: 04 May 2001 15:11:37 +0200 [thread overview]
Message-ID: <jer8y52r92.fsf@hawking.suse.de> (raw)
In-Reply-To: <8541.988980403@ocs3.ocs-net>
In-Reply-To: <8541.988980403@ocs3.ocs-net> (Keith Owens's message of "Fri, 04 May 2001 22:46:43 +1000")
Keith Owens <kaos@ocs.com.au> writes:
|> On Fri, 04 May 2001 07:34:20 -0500,
|> Todd Inglett <tinglett@vnet.ibm.com> wrote:
|> >But this is where hell breaks loose. Every process has a valid parent
|> >-- unless it is dead and nobody cares. Process N has already exited and
|> >released from the tasklist while its parent was still alive. There was
|> >no reason to reparent it. It just got released. So N's task_struct has
|> >a dangling ptr to its parent. Nobody is holding the parent task_struct,
|> >either. When the parent died memory for its task_struct was released.
|> >This is ungood.
|>
|> Wrap the reference to the parent task structure with exception table
|> recovery code, like copy_from_user().
Exception tables only protect accesses to user virtual memory. Kernel
memory references must always be valid in the first place.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-05-04 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 14:30 SMP races in proc with thread_struct Todd Inglett
2001-05-01 16:50 ` Alexander Viro
2001-05-03 11:47 ` Todd Inglett
2001-05-04 12:34 ` Todd Inglett
2001-05-04 12:46 ` Keith Owens
2001-05-04 13:11 ` Andreas Schwab [this message]
2001-05-04 13:38 ` Brian Gerst
2001-05-04 23:27 ` Keith Owens
2001-05-04 14:21 ` Andreas Ferber
2001-05-04 15:18 ` Todd Inglett
2001-05-04 16:04 ` Alexander Viro
2001-05-04 17:52 ` [PATCH][RFC] " Alexander Viro
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=jer8y52r92.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=tinglett@vnet.ibm.com \
--cc=viro@math.psu.edu \
/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