From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Anand Jahagirdar" <anandjigar@gmail.com>
Cc: "Krzysztof Halasa" <khc@pm.waw.pl>, linux-kernel@vger.kernel.org
Subject: Re: Fork Bombing Patch
Date: Mon, 20 Aug 2007 16:38:41 +0200 [thread overview]
Message-ID: <9a8748490708200738o36374d63ib5c71d5dc8dc9978@mail.gmail.com> (raw)
In-Reply-To: <25ae38200708200726tdf097b1kcd0269cf11c53bf3@mail.gmail.com>
(please don't top-post)
On 20/08/07, Anand Jahagirdar <anandjigar@gmail.com> wrote:
> Hi
> I think Its not worth to make it configurable just for one printk
> statement. am i missing something?
>
I think you are missing the fact that there are lots of situations
where users may hit the configured process limit without that being an
indication of a fork bomb (or other) attack.
This means that there will be many systems that will trigger your
warning where there really is no problem. That's a good reason for a)
making the message KERN_INFO and b) let administrators somehow disable
it completely.
Personally I'm wondering if we even want/need this at all.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2007-08-20 14:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 6:24 Anand Jahagirdar
2007-08-16 7:40 ` Petr Tesarik
2007-08-17 7:19 ` Paul Jackson
2007-08-17 7:42 ` Petr Tesarik
2007-08-17 9:05 ` Paul Jackson
2007-08-16 11:19 ` Krzysztof Halasa
2007-08-16 11:27 ` Jan Engelhardt
2007-08-20 14:26 ` Anand Jahagirdar
2007-08-20 14:38 ` Jesper Juhl [this message]
2007-08-16 21:06 ` Chris Snook
2007-08-20 14:24 ` Anand Jahagirdar
2007-08-20 14:42 ` Chris Snook
2007-08-22 6:17 ` Anand Jahagirdar
2007-08-23 11:52 ` Krzysztof Halasa
2007-08-23 19:01 ` Chris Snook
2007-08-23 21:47 ` Krzysztof Halasa
[not found] ` <7b9198260708231737t33923ec6yde48bb1338a6fa70@mail.gmail.com>
2007-08-24 0:37 ` Tom Spink
2007-08-29 9:48 ` Anand Jahagirdar
2007-08-29 11:29 ` Simon Arlott
2007-08-29 11:54 ` Anand Jahagirdar
2007-08-29 13:49 ` Chris Snook
2007-09-02 8:52 ` Kyle Moffett
[not found] ` <25ae38200806180502i4d78e240l210b261f05f10507@mail.gmail.com>
[not found] ` <25ae38200806180505m61d51440ma5754fa817dfbc0b@mail.gmail.com>
2008-06-18 13:39 ` Chris Snook
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=9a8748490708200738o36374d63ib5c71d5dc8dc9978@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=anandjigar@gmail.com \
--cc=khc@pm.waw.pl \
--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®