Date: Thu, 4 Jan 2001 22:08:59 -0800 From: "Jeremiah Gowdy" <jgowdy@home.com> To: "Alfred Perlstein" <bright@wintelcom.net>, "Michael Wells" <michael@wells.org.uk> Cc: <freebsd-questions@FreeBSD.ORG> Subject: Re: SMP kernel overheats Message-ID: <004d01c076dd$fe71e160$aa240018@vista1.sdca.home.com> References: <20010104191237.A580@wells.org.uk> <20010104111913.B292@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> While it would be a nice feature, anyone depending on it is not being
> very bright about it. Basically, you don't want a machine that's
> vulnerable to a "while bomb":
>
> while (1)
> ;
>
> :)
"while bomb" my ass. As I demonstrated at ToorCon's RootWars contest, most
people don't have login.conf set properly so this works nicely:
void main(void)
{
while (1)
{
malloc(1024000);
fork();
}
}
This fork()/malloc() bomb will put your box at super unbelievable loads
(I've seen 200+), completely fill your proc table like any other fork, but
then it will also use all your memory, causing massive swapping and the
eventual inability to use the box either locally or via shelling in. Any
box without login.conf protection will die. If you don't have proper
cooling, this will overheat your cpus, and if you don't have bios protection
it will probably ruin them.
And yes, I was disqualified from ToorCon's Rootwars. :)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004d01c076dd$fe71e160$aa240018>