From: Paul Larson <plars@austin.ibm.com>
To: Marcelo Tosati <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] Fix for get_pid hang
Date: 07 Mar 2002 16:25:24 -0600 [thread overview]
Message-ID: <1015539925.16835.22.camel@plars.austin.ibm.com> (raw)
In-Reply-To: <1015539061.16836.10.camel@plars.austin.ibm.com>
In-Reply-To: <200203072045.PAA08386@egenera.com> <1015539061.16836.10.camel@plars.austin.ibm.com>
Ok, this time with the patch for real. :)
On Thu, 2002-03-07 at 16:11, Paul Larson wrote:
> On Thu, 2002-03-07 at 14:45, Patrick O'Rourke wrote:
> > It is possible on large memory systems that the default process limits
> > can exceed PID_MAX. This will allow a non-root user to consume all pids
> > resulting in the kernel to basically hang in get_pid().
> >
>
> > + /* don't let threads go beyond PID_MAX */
> > + if (max_threads > PID_MAX) {
> > + max_threads = PID_MAX;
> > + }
> > +
> The problem with this approach is that it doesn't take into account
> pgrp, tgids, etc... I submitted the following patch a couple of weeks
> ago that fixes the problem a better way.
>
> Thanks,
> Paul Larson
Marcelo, any chance of getting this accepted into the next 2.4.19-pre?
It is obviously a bug that is afecting several others as well. I think
the LSE team is looking at some performance enhancements to get_pid, but
from what I've seen so far they will be working on top of this bug fix.
I just verified that the patch still applies cleanly against
2.4.19-pre2.
Thanks,
Paul Larson
diff -Naur linux-2.4.18-rc2/kernel/fork.c linux-getpid/kernel/fork.c
--- linux-2.4.18-rc2/kernel/fork.c Wed Feb 20 09:54:39 2002
+++ linux-getpid/kernel/fork.c Fri Feb 22 15:52:52 2002
@@ -20,6 +20,7 @@
#include <linux/vmalloc.h>
#include <linux/completion.h>
#include <linux/personality.h>
+#include <linux/compiler.h>
#include <asm/pgtable.h>
#include <asm/pgalloc.h>
@@ -85,12 +86,13 @@
{
static int next_safe = PID_MAX;
struct task_struct *p;
- int pid;
+ int pid, beginpid;
if (flags & CLONE_PID)
return current->pid;
spin_lock(&lastpid_lock);
+ beginpid = last_pid;
if((++last_pid) & 0xffff8000) {
last_pid = 300; /* Skip daemons etc. */
goto inside;
@@ -110,12 +112,16 @@
last_pid = 300;
next_safe = PID_MAX;
}
+ if(unlikely(last_pid == beginpid))
+ goto nomorepids;
goto repeat;
}
if(p->pid > last_pid && next_safe > p->pid)
next_safe = p->pid;
if(p->pgrp > last_pid && next_safe > p->pgrp)
next_safe = p->pgrp;
+ if(p->tgid > last_pid && next_safe > p->tgid)
+ next_safe = p->tgid;
if(p->session > last_pid && next_safe > p->session)
next_safe = p->session;
}
@@ -125,6 +131,11 @@
spin_unlock(&lastpid_lock);
return pid;
+
+nomorepids:
+ read_unlock(&tasklist_lock);
+ spin_unlock(&lastpid_lock);
+ return 0;
}
static inline int dup_mmap(struct mm_struct * mm)
@@ -620,6 +631,8 @@
copy_flags(clone_flags, p);
p->pid = get_pid(clone_flags);
+ if (p->pid == 0 && current->pid != 0)
+ goto bad_fork_cleanup;
p->run_list.next = NULL;
p->run_list.prev = NULL;
next prev parent reply other threads:[~2002-03-07 22:27 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 [this message]
2002-03-08 15:02 ` Patrick O'Rourke
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=1015539925.16835.22.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®