mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bodo Eggert <7eggert@gmx.de>
To: Anand Jahagirdar <anandjigar@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Patch Related With Fork Bombing Attack
Date: Thu, 28 Jun 2007 00:14:08 +0200	[thread overview]
Message-ID: <E1I3fm4-00010y-NL@be1.lrz> (raw)
In-Reply-To: <8Alj9-41R-7@gated-at.bofh.it>

(not CCing security, since it's not a security bug and it's too late to
 verify if they should be on cc. Will do later.)

Anand Jahagirdar <anandjigar@gmail.com> wrote:

> This patch Warns the administrator about the fork bombing attack
> (whenever any user is crossing its process limit). I have used
> printk_ratelimit function in this patch. This function helps to
> prevent flooding of syslog and prints message as per the values set by
> root user in following files:-
> 
> 1) /proc/sys/kernel/printk_ratelimit:- This file contains value for,
> how many times message should be printed in syslog.
[...]

I'm wondering: Can these ratelimits be used to tell real forkbombs from
normal oops-i-hit-the-limits? I imagine if you have your private ratelimit,
that might just do the trick.

Beware: I have no idea on how much such an extra ratelimit would cost, and if
having that ratelimit-based detector would actually be a gain.
-- 
Ever notice how fast Windows runs? Neither did I. 

Friß, Spammer: .w@7eggert.dyndns.org N@zu.0vJB.7eggert.dyndns.org
 99aLZMlkFe@YE.7eggert.dyndns.org Bbga@PKDpIYua.7eggert.dyndns.org

       reply	other threads:[~2007-06-27 22:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8Alj9-41R-7@gated-at.bofh.it>
2007-06-27 22:14 ` Bodo Eggert [this message]
2007-07-13 12:39 Patch Related with " Anand Jahagirdar
2007-07-14  9:40 ` WANG Cong
2007-07-15  8:48 ` Simon Arlott
  -- strict thread matches above, loose matches on Subject: below --
2007-06-26 15:32 Patch Related With " Anand Jahagirdar

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=E1I3fm4-00010y-NL@be1.lrz \
    --to=7eggert@gmx.de \
    --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

all inboxes | Powered by JetHome®