From: Valdis.Kletnieks@vt.edu
To: Anand Jahagirdar <anandjigar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fork Bombing Attack
Date: Thu, 17 May 2007 11:01:45 -0400 [thread overview]
Message-ID: <4051.1179414105@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 17 May 2007 20:15:32 +0530." <25ae38200705170745t4a80e7eer413b3c2bb0c5a327@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On Thu, 17 May 2007 20:15:32 +0530, Anand Jahagirdar said:
> Hello All
> I have set per user process limit ( ulimit) for both
> root and guest account as 8000 by using option ulimit -u 8000.this is
> Hard limit. still fork bombing attack killed the box and machine
> needed reboot. will any body please tell me why this is so? i have
> tried all this attack on machine with FC6 and Linux kernel 2.6.18.
Convince me that your machine in fact has sufficient resources to spawn 8000
processes.
Then retry it with "ulimit -u 100", and then do a binary search from 100 to 8000
to find out what value it stops working at.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-05-17 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 14:45 Fork Bombing Attack Anand Jahagirdar
2007-05-17 15:01 ` Valdis.Kletnieks [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2007-05-17 7:25 Fork bombing Attack Anand Jahagirdar
2007-05-17 7:39 ` Marat Buharov
2007-05-17 9:07 ` 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=4051.1179414105@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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).