mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Federico Sevilla III <jijo@free.net.ph>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Very large font size crashing X Font Server and Grounding Server to a Halt (was: remote DoS in Mozilla 1.0)
Date: Thu, 13 Jun 2002 10:18:06 +0300	[thread overview]
Message-ID: <20020613101806.F19520@mea-ext.zmailer.org> (raw)
In-Reply-To: <20020610102006.A6947@lemuria.org> <Pine.LNX.4.44.0206130908550.985-100000@kalabaw>

On Thu, Jun 13, 2002 at 09:44:33AM +0800, Federico Sevilla III wrote:
> From:	Federico Sevilla III <jijo@free.net.ph>
> To:	BugTraq Mailing List <bugtraq@securityfocus.com>,
> 	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> 
> (Note: bug originally posted on BugTraq, this response is cross-posted to
> the LKML because of the way the server hosting the X font server ground to
> a halt.)

  It really is nothing new.  (Besides of XFree86's Type1 engine calling 
  abort() when it does not like to do something ..)
...
> Suggestions on how to work around this on multiple levels would definitely
> be appreciated. I'll be starting by removing the X font server from our
> file and authentication server onto some high-powered workstation, but I'm
> sure this won't be enough, and knowing that a user process like xfs-daemon
> can drag the Linux kernel down to knees is not very comforting. :(

  ANY very big program with active working set larger than memory size
  has problems at Linux / Linux has problems handling it.  Indeed the
  problem is _not_ new, nor trivial to solve efficiently.  The ultimate
  situation is called "trashing", where a program to proceed a page of
  code needs to be moved into memory, and to make room for that, some
  other program page must be moved out..  What makes the issue more
  difficult is that the memory is used for lots and lots of different
  kinds of buffers and caches as well, and playing a balancing act on
  them all is quite difficult.

  This is recurring topic at  linux-kernel  list, and has its own
  list called  linux-mm  (not at vger, though.)

  Others may have different views on the issue, but I think that:
     2.0:        fairly tolerable OOM/trashing behaviour
     2.2:        got worse
     2.4.early:  rather terrible
     2.4.late:   improved somewhat, roughly in par with 2.2

>  --> Jijo
> - -- 
> Federico Sevilla III   :  <http://jijo.free.net.ph/>
...
> Please read the FAQ at  http://www.tux.org/lkml/

/Matti Aarnio

  parent reply	other threads:[~2002-06-13  7:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020610102006.A6947@lemuria.org>
2002-06-13  1:44 ` Federico Sevilla III
2002-06-13  5:39   ` Very large font size crashing X Font Server and Grounding Server to Alan Cox
2002-06-13  5:57     ` rlimits and non overcommit (was: Very large font size ...) Federico Sevilla III
2002-06-13  6:11       ` Keith Owens
2002-06-13  9:25         ` rlimits and non overcommit Federico Sevilla III
2002-06-13  7:18   ` Matti Aarnio [this message]
2002-06-13 16:26   ` Very large font size crashing X Font Server and Grounding Server to a Halt (was: remote DoS in Mozilla 1.0) rjh
2002-06-14 13:50     ` Security Coordinator
2002-06-13 21:10   ` Matthew Wakeling
2002-06-13 22:33     ` Very large font size crashing X Font Server and Grounding Server to a Halt Bernd Eckenfels
2002-06-13 16:53 Very large font size crashing X Font Server and Grounding Server to a Halt (was: remote DoS in Mozilla 1.0) Melchior FRANZ
2002-06-13 17:17 Melchior FRANZ
2002-06-13 17:34 ` Billy O'Connor
2002-06-13 18:44   ` Melchior FRANZ
2002-06-13 21:47 Jesse Pollard
2002-06-13 22:09 ` Matthew Wakeling
2002-06-14 13:46 Juliusz Chroboczek
2002-06-22  1:36 ` Alan Cox

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=20020613101806.F19520@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=jijo@free.net.ph \
    --cc=linux-kernel@vger.kernel.org \
    /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®