From: Keith Owens <kaos@ocs.com.au>
To: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
Cc: Dave Hansen <haveblue@us.ibm.com>,
Kasper Dupont <kasperd@daimi.au.dk>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Race condition?
Date: Sat, 03 Aug 2002 21:17:23 +1000 [thread overview]
Message-ID: <2324.1028373443@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 03 Aug 2002 21:07:11 +1000." <2020.1028372831@ocs3.intra.ocs.com.au>
On Sat, 03 Aug 2002 21:07:11 +1000,
Keith Owens <kaos@ocs.com.au> wrote:
>On Sat, 3 Aug 2002 12:08:28 +0200,
>Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de> wrote:
>>Anyway this code can corrupt the global variable nr_threads.
>>Without the BKL it is buggy, so it has to be fixed anyway and we
>>can do it right.
>
>nr_threads is protected by tasklist_lock. How on earth can fuzzy
>counting on user->processes corrupt nr_threads?
Never mind. Checking and updating nr_threads is a seperate race from
the one on user->processes. The nr_threads race is a problem that
needs to be fixed.
next prev parent reply other threads:[~2002-08-03 11:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17aw0S-0U7gB7C@fmrl00.sul.t-online.com>
2002-08-03 11:07 ` Keith Owens
2002-08-03 11:17 ` Keith Owens [this message]
2002-08-02 13:46 Kasper Dupont
2002-08-02 14:48 ` Oliver Neukum
2002-08-02 17:13 ` Kasper Dupont
2002-08-02 18:51 ` Oliver Neukum
2002-08-02 17:37 ` Dave Hansen
2002-08-02 18:45 ` Oliver Neukum
2002-08-02 19:09 ` Dave Hansen
2002-08-02 17:00 ` Dave Hansen
2002-08-02 17:41 ` Oliver Neukum
2002-08-02 18:48 ` Dave Hansen
2002-08-02 18:56 ` Dave Hansen
2002-08-03 0:36 ` Keith Owens
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=2324.1028373443@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=haveblue@us.ibm.com \
--cc=kasperd@daimi.au.dk \
--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®