From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Q: nr_threads locking
Date: Mon, 21 Apr 2003 15:25:39 +0200 [thread overview]
Message-ID: <3EA3F153.3000106@colorfullife.com> (raw)
Hi Andrew,
According to the comments, nr_threads is protected by lock_kernel, but
do_fork() runs without the bkl for ages.
Would it be possible to use your percpu_counters for nr_threads? It
seems to be used only to guard against fork bombs and for i_nlink of /proc.
--
Manfred
next reply other threads:[~2003-04-21 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 13:25 Manfred Spraul [this message]
2003-04-21 18:28 ` Q: nr_threads locking Andrew Morton
2003-04-21 18:49 ` Manfred Spraul
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=3EA3F153.3000106@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@digeo.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