From: David Schwartz <davids@webmaster.com>
To: <knuffie@xs4all.nl>, Rik van Riel <riel@conectiva.com.br>
Cc: Krzysztof Rusocki <kszysiu@main.braxis.co.uk>,
<linux-xfs@oss.sgi.com>, <linux-kernel@vger.kernel.org>
Subject: Re: %u-order allocation failed
Date: Fri, 5 Oct 2001 15:06:25 -0700 [thread overview]
Message-ID: <20011005220627.AAA22897@shell.webmaster.com@whenever> (raw)
In-Reply-To: <Pine.BSI.4.10.10110052208390.303-100000@xs3.xs4all.nl>
>The system is beafy enough to tolerate something mundane as this. It should
>definitely not die.
A fork bomb with no limits attempts to create an infinite number of
processes. No system can be that beefy.
DS
next prev parent reply other threads:[~2001-10-05 22:06 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-05 11:07 %u-order allocation failed Krzysztof Rusocki
2001-10-05 11:59 ` Rik van Riel
2001-10-05 20:18 ` Seth Mos
2001-10-05 20:22 ` Rik van Riel
2001-10-05 20:31 ` Seth Mos
2001-10-05 20:43 ` Steve Lord
2001-10-05 21:09 ` Seth Mos
2001-10-05 22:06 ` David Schwartz [this message]
2001-10-05 22:16 ` Seth Mos
2001-10-06 14:00 ` Mikulas Patocka
2001-10-06 14:03 ` Rik van Riel
2001-10-06 14:44 ` Mikulas Patocka
2001-10-06 15:31 ` Mikulas Patocka
2001-10-06 19:05 ` Mikulas Patocka
2001-10-06 16:58 ` Rik van Riel
2001-10-06 17:48 ` Mikulas Patocka
2001-10-06 18:12 ` Anton Blanchard
2001-10-06 19:07 ` Mikulas Patocka
2001-10-06 20:13 ` Benjamin Herrenschmidt
2001-10-06 22:34 ` Mikulas Patocka
2001-10-07 1:23 ` Rik van Riel
2001-10-07 11:12 ` Benjamin Herrenschmidt
2001-10-06 21:13 ` Alan Cox
2001-10-06 22:31 ` Mikulas Patocka
2001-10-06 22:42 ` Alan Cox
2001-10-06 22:58 ` Mikulas Patocka
[not found] ` <Pine.LNX.3.96.1011007003803.18004D-100000@artax.karlin.mff.cuni .cz>
2001-10-06 23:36 ` Alex Bligh - linux-kernel
[not found] ` <Pine.LNX.3.96.1011007002406.18004A-100000@artax.karlin.mff.cuni .cz>
2001-10-06 23:34 ` Alex Bligh - linux-kernel
2001-10-07 7:35 ` Pavel Machek
[not found] ` <Pine.LNX.3.96.1011006164044.29342B-200000@artax.karlin.mff.cuni .cz>
2001-10-06 17:59 ` Alex Bligh - linux-kernel
2001-10-06 19:13 ` Mikulas Patocka
2001-10-06 19:22 ` arjan
2001-10-06 22:36 ` Mikulas Patocka
[not found] ` <Pine.LNX.3.96.1011006210743.7808D-100000@artax.karlin.mff.cuni. cz>
2001-10-06 23:26 ` Alex Bligh - linux-kernel
2001-10-07 18:30 ` Eric W. Biederman
2001-10-08 15:01 ` Alex Bligh - linux-kernel
2001-10-07 18:32 ` Eric W. Biederman
2001-10-07 9:40 ` Alan Cox
2001-10-07 12:28 ` Mikulas Patocka
2001-10-07 14:12 ` Alan Cox
2001-10-07 15:42 ` Mikulas Patocka
2001-10-07 22:01 ` Alan Cox
2001-10-08 15:08 ` Alex Bligh - linux-kernel
2001-10-08 16:44 ` Pavel Machek
2001-10-08 22:21 ` Mikulas Patocka
2001-10-08 21:16 ` David Lang
[not found] ` <Pine.LNX.3.96.1011009001720.20446A-100000@artax.karlin.mff.cuni .cz>
2001-10-08 22:53 ` Alex Bligh - linux-kernel
2001-10-08 23:31 ` Mikulas Patocka
2001-10-08 23:44 ` Alan Cox
2001-10-08 23:46 ` Mikulas Patocka
2001-10-09 9:45 ` Pavel Machek
2001-10-08 23:48 ` Linus Torvalds
2001-10-08 23:54 ` Mikulas Patocka
2001-10-09 11:48 ` Rik van Riel
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=20011005220627.AAA22897@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=knuffie@xs4all.nl \
--cc=kszysiu@main.braxis.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=riel@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