mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Swiedler" <ceswiedler_lk@mindspring.com>
To: "Szabolcs Szakacsits" <szaka@f-secure.com>,
	<linux-kernel@vger.kernel.org>
Cc: "Erik Mouw" <J.A.K.Mouw@ITS.TUDelft.NL>
Subject: RE: [PATCH] Re: reliability of linux-vm subsystem
Date: Tue, 14 Nov 2000 10:24:21 -0500	[thread overview]
Message-ID: <NDBBIAJKLMMHOGKNMGFNGEJECPAA.ceswiedler_lk@mindspring.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0011132116420.20626-100000@fs129-190.f-secure.com>

> > Good, so the OOM killer works.
>
> But it doesn't work for this kind of application misbehaviours (or
> user attacks):
>
> main() { while(1) if (fork()) malloc(1); }

This seems to be a fork() bomb, not a VM issue. The system is overwhelmed by
the the forks, not by the space consumed by the allocations themselves. For
one thing, I've found that

main() { while(1) malloc(1024*1024); }

does not kill your system very quickly (if at all). Without actually writing
to the memory, it doesn't seem to be "really" allocated. Adding a memset()
will kill your system much more quickly.

chris

-
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/

      parent reply	other threads:[~2000-11-14 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-13 21:50 Szabolcs Szakacsits
2000-11-13 23:45 ` Erik Mouw
2000-11-14  0:53   ` Michael Peddemors
2000-11-14  9:28     ` Helge Hafting
2000-11-14 13:55   ` Szabolcs Szakacsits
2000-11-14 15:24 ` Chris Swiedler [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=NDBBIAJKLMMHOGKNMGFNGEJECPAA.ceswiedler_lk@mindspring.com \
    --to=ceswiedler_lk@mindspring.com \
    --cc=J.A.K.Mouw@ITS.TUDelft.NL \
    --cc=linux-kernel@vger.kernel.org \
    --cc=szaka@f-secure.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

all inboxes | Powered by JetHome®