linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Anand Jahagirdar" <anandjigar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fork bombing Attack
Date: Thu, 17 May 2007 10:07:03 +0100	[thread overview]
Message-ID: <20070517100703.01577558@the-village.bc.nu> (raw)
In-Reply-To: <25ae38200705170025m23fe8ea9s81515ec8d1a0a137@mail.gmail.com>

On Thu, 17 May 2007 12:55:53 +0530
"Anand Jahagirdar" <anandjigar@gmail.com> wrote:

> Dear Sir,
>              I just want to know whether fork bombing attack still
> exist on the machine having Distribution as Fedora Core 6 and Linux
> Kernel 2.6.x.?
> 
>            additional Info :  I have set ulimit as 8000 and loged in
> as Guest User on machine having Distribution as Fedora Core 6 and
> Linux kernel 2.6.18. simple fork bombing program while(1) fork();
> killed the box and machine needed reboot. will any body please tell me
> why fork bombing attack killed the box even after setting ulimit as
> 8000?

Did you set a sensible per user process limit and what swap/memory setup
do you have. If you have sensible per user process limits and zero
overcommit setup you shouldn't be able to do anything beyond soak up a
lot of CPU time.

  parent reply	other threads:[~2007-05-17  9:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17  7:25 Fork bombing Attack Anand Jahagirdar
2007-05-17  7:39 ` Marat Buharov
2007-05-17  9:07 ` Alan Cox [this message]
2007-05-17 14:45 Fork Bombing Attack Anand Jahagirdar
2007-05-17 15:01 ` Valdis.Kletnieks
2007-05-18 11:13   ` Anand Jahagirdar
2007-05-18 13:07     ` Michael Tokarev
2007-05-18 13:19     ` Ahmed S. Darwish
2007-05-18 17:22       ` Anand Jahagirdar
2007-05-18 17:49         ` Valdis.Kletnieks
2007-05-18 21:21         ` Krzysztof Halasa
2007-05-18 22:40         ` Bernd Eckenfels
2007-05-22 21:52     ` Mark Lord

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=20070517100703.01577558@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=anandjigar@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).