From: Krzysztof Halasa <khc@pm.waw.pl>
To: Chris Snook <csnook@redhat.com>
Cc: Anand Jahagirdar <anandjigar@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Fork Bombing Patch
Date: Thu, 23 Aug 2007 23:47:22 +0200 [thread overview]
Message-ID: <m34pipgbyt.fsf@maximus.localdomain> (raw)
In-Reply-To: <46CDD98F.2020208@redhat.com> (Chris Snook's message of "Thu, 23 Aug 2007 15:01:35 -0400")
Chris Snook <csnook@redhat.com> writes:
> Wrapping a single printk that's unrelated to debugging in an #ifdef
> CONFIG_* or a sysctl strikes me as abuse of those configuration
> facilities.
Abuse, probably not (if a thing is required on one system and must
not be on another, it has to be configurable). If the printk is
a good idea... IMHO hardly, at best. We don't warn about trying to
write to /vmlinuz after all.
ulimit/pam_limits should fix the (IMHO nonexistent) problem nicely.
One has to plug all the holes, though (e.g. $HOME/.forward).
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-08-23 21:47 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
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 [this message]
[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=m34pipgbyt.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=anandjigar@gmail.com \
--cc=csnook@redhat.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®