public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: Matthew Wakeling <mnw21@bigfoot.com>, linux-kernel@vger.kernel.org
Subject: Re: Very large font size crashing X Font Server and Grounding Serverto a  Halt (was: remote DoS in Mozilla 1.0)
Date: Fri, 14 Jun 2002 13:06:45 +0200	[thread overview]
Message-ID: <3D09CE45.C2D8152B@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0206132255220.4999-100000@server3.jumpleads.com>

Matthew Wakeling wrote:
[...]
> However, one circumstance that throwing lots of swap around doesn't
> fix is when a process has an insatiable need for memory. In this case,
> either the process grows very quickly, or is just plain big. I think the
> out-of-memory killer should target big or growing processes. If it doesn't
> hit the correct process the first time, it will free up a lot more RAM
> than it would otherwise, and it would be likely to get it right the second
> time.
> 
A fork bomb would kill everything else in your machine then.  The bomb
program doesn't grow and is smaller than anythine else - but there's 
so many of them.  So all the other useful programs, 
including shells, are killed. :-(

Helge Hafting

      parent reply	other threads:[~2002-06-14 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 21:47 Very large font size crashing X Font Server and Grounding Server to a Halt (was: remote DoS in Mozilla 1.0) Jesse Pollard
2002-06-13 22:09 ` Matthew Wakeling
2002-06-14 10:44   ` Very large font size crashing X Font Server and Grounding Serverto " Bryan Andersen
2002-06-14 11:06   ` Helge Hafting [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=3D09CE45.C2D8152B@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mnw21@bigfoot.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