public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Patrick O'Rourke" <porourke@egenera.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: Marcelo Tosati <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix for get_pid hang
Date: Fri, 08 Mar 2002 10:02:59 -0500	[thread overview]
Message-ID: <3C88D2A3.60201@egenera.com> (raw)
In-Reply-To: <200203072045.PAA08386@egenera.com> 	<1015539061.16836.10.camel@plars.austin.ibm.com> <1015539925.16835.22.camel@plars.austin.ibm.com>

Paul Larson wrote:
> Ok, this time with the patch for real. :)

While I agree with your patch, I still think something should be
done in fork_init() to restrict the initial value of max_threads.

We should not rely on the amount of memory alone.

For example, after a fresh reboot on an i386 system with 12gb
of ram we get:

	[joeuser@simpsons-lisa joeuser]$ id
	uid=500(joeuser) gid=500(joeuser) groups=500(joeuser)
	[joeuser@simpsons-lisa joeuser]$ ulimit -a
	core file size (blocks)     1000000
	data seg size (kbytes)      unlimited
	file size (blocks)          unlimited
	max locked memory (kbytes)  unlimited
	max memory size (kbytes)    unlimited
	open files                  1024
	pipe size (512 bytes)       8
	stack size (kbytes)         8192
	cpu time (seconds)          unlimited
	max user processes          49152
	virtual memory (kbytes)     unlimited
	[joeuser@simpsons-lisa joeuser]$

I believe it is wrong for max user processes to start off above PID_MAX.

Pat

-- 
Patrick O'Rourke
porourke@egenera.com


      reply	other threads:[~2002-03-08 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 20:45 [PATCH] Prevent max_threads from exceeding PID_MAX Patrick O'Rourke
2002-03-07 22:11 ` Paul Larson
2002-03-07 22:23   ` [PATCH] Fix for get_pid hang Paul Larson
2002-03-07 22:25   ` Paul Larson
2002-03-08 15:02     ` Patrick O'Rourke [this message]

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=3C88D2A3.60201@egenera.com \
    --to=porourke@egenera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=plars@austin.ibm.com \
    /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