public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred <manfred@colorfullife.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Andries Brouwer <aeb@veritas.com>,
	linux-kernel@vger.kernel.org, tytso@mit.edu,
	torvalds@transmeta.com
Subject: Re: minor bugs around fork_init
Date: Tue, 26 Dec 2000 13:06:15 +0100	[thread overview]
Message-ID: <3A4889B7.D13DD3@colorfullife.com> (raw)
In-Reply-To: <3A44D3F3.522AD08A@colorfullife.com> <20001223233806.A886@veritas.com> <20001224212331.A531@bug.ucw.cz>

Pavel Machek wrote:
> 
> Hi!
> 
> > > * get_pid causes a deadlock when all pid numbers are in use.
> > > In the worst case, only 10900 threads are required to exhaust
> > > the 15 bit pid space.
> >
> > Yes. I posted a patch for 31-bit pids once or twice.
> > There is no great hurry, but on the other hand, it is always
> > better to make these changes long before it is really urgent.
> 
> On 2Gig machine, you should be able to overflow 16 bits. So it is
> quite urgent.

That's another problem!
31 bit uid would be a nice feature for 2.4, but the last time I asked
Linus he answered that the high bits are still reserved.

My patch fixes bugs in the current, 15 bit implementation:
* we don't reserve any threads for root as 2.2 did
* if a user limit allows for > 10900 threads, then that user can cause a
deadlock by using all pid values (one thread can block 3 pid values).
get_pid() will loop forever.
* in theory, 2 threads could get the same pid.

--
	Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-12-26 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-23 16:33 minor bugs around fork_init Manfred
2000-12-23 17:12 ` test13-pre4 fails to compile ebi4
2000-12-23 18:12   ` Kai Germaschewski
2000-12-23 22:38 ` minor bugs around fork_init Andries Brouwer
2000-12-24 20:23   ` Pavel Machek
2000-12-26 12:06     ` Manfred [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=3A4889B7.D13DD3@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=aeb@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=torvalds@transmeta.com \
    --cc=tytso@mit.edu \
    /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