From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: bug w/ threads-max, pid_max, & /proc
Date: 23 Sep 2003 17:23:13 -0400 [thread overview]
Message-ID: <1064352192.740.3063.camel@cube> (raw)
Plain 2.6.0-test5 is affected. (so don't blame me)
The /proc filesystem gets really messed up when you
create more threads than you have PID values. Yes,
you can do this. I created 40000 threads on a system
with pid_max of 32768 and a threads-max of 98304.
This should not be allowed, for obvious reasons, and
because it breaks the /proc filesystem. Doing a
simple "/bin/ls /proc" would return 0, 1, or 2 of
every file. Stuff like /proc/cpuinfo was affected,
not just the process directories.
next reply other threads:[~2003-09-23 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 21:23 Albert Cahalan [this message]
2003-09-23 22:58 ` bug w/ threads-max, pid_max, & /proc William Lee Irwin III
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=1064352192.740.3063.camel@cube \
--to=albert@users.sf.net \
--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 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.