From: Martin Olsson <mnemo@minimum.se>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
Ubuntu Devel Discuss <ubuntu-devel-discuss@lists.ubuntu.com>
Subject: Re: Is it possible to give the user the option to cancel forkbombs?
Date: Fri, 16 Nov 2007 23:04:48 -0800 [thread overview]
Message-ID: <473E9290.3040006@minimum.se> (raw)
In-Reply-To: <20071116213137.6efe3f9e@the-village.bc.nu>
Sorry about that, I checked the "has security impact" checkbox and that
marked it as private by default. This is a very well known problem
though so keeping secret certainly does not make sense. I have manually
removed the "private" flag now.
The content of the bug report was as follows:
---------------------------------------------
Repro steps:
1. Install gutsy gibbon (or probably any ubuntu)
2. Start a gnome terminal
3. Run this command:
:(){ :|:& };:
4. Ubuntu starts to work furiously, after less than a second terminal
gets flooded with "low resources" message, and within a few seconds the
whole machine breaks down complete to the point where no a single pixel
is updated and the mouse cannot be moved at all. It's not possible to
escape to a ALT-Fn console terminal and CTRL-ALT-DEL does not work.
Okay, so this is not as bad as winnuke.exe because it's not remote but I
just did it on my shared hosting co and their server went down. And I
mean seriously, there should be a way for a user to abort stuff that
hogs resources this type of complete breakdown is NEVER acceptible. I
had to power of the machine and my file system got royally screwed (long
fsck etc).
Some of you might say this is like the oldest trick in the book, yada
yada yada...
Martin
Alan Cox wrote:
> On Fri, 16 Nov 2007 21:51:27 -0800
> Martin Olsson <mnemo@minimum.se> wrote:
>
>> Dear kernel hackers,
>>
>> This is a message from below 0x7FFFFFFF. Please look at this bug (it's
>> not a new concept but still):
>> https://bugs.launchpad.net/ubuntu/+bug/163185
>
> It seems to want people to register to view it. I guess Ubuntu should fix
> launchpad then we can see the bug report
>
> Alan
> -
next prev parent reply other threads:[~2007-11-16 22:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-17 5:51 Is it possible to give the user the option to cancel forkbombs? Martin Olsson
2007-11-16 21:31 ` Alan Cox
2007-11-17 7:04 ` Martin Olsson [this message]
2007-11-16 23:46 ` Alan Cox
2007-11-17 6:45 ` Dane Mutters
2007-11-17 7:44 ` Peter Zijlstra
2007-11-17 10:39 ` Alan Cox
2007-11-17 13:36 ` Andi Kleen
2007-11-17 15:28 ` Herbert Xu
2007-11-17 17:42 ` Martin Olsson
2007-11-17 10:03 ` Peter Zijlstra
2007-11-17 15:53 ` Diego Calleja
2007-11-17 17:55 ` Dane Mutters
2007-11-23 7:34 ` Radoslaw Szkodzinski
2007-11-22 0:05 ` (``-_-´´) -- Fernando
2007-11-22 12:03 ` David Newall
2007-11-16 21:38 ` Diego Calleja
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=473E9290.3040006@minimum.se \
--to=mnemo@minimum.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ubuntu-devel-discuss@lists.ubuntu.com \
/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