Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 May 2006 07:36:24 GMT
From:      Matthieu MICHAUD <ohmer@epita.info>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/97591: 6.1-RELEASE crashes on fork bomb
Message-ID:  <200605220736.k4M7aOuk091200@www.freebsd.org>
Resent-Message-ID: <200605220740.k4M7eE8V017784@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         97591
>Category:       kern
>Synopsis:       6.1-RELEASE crashes on fork bomb
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon May 22 07:40:13 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Matthieu MICHAUD
>Release:        6.1-RELEASE
>Organization:
EPITA
>Environment:
FreeBSD moe.lan 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Mon May 15 20:12:38 CEST 2006 root@homer.cload.net:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
my fresh installed 6.1-RELEASE workstation doesn't survive to a simple fork bomb. after launching the bomb, it freezes a few seconds and then my computer reboots. afair, 5.4 systems survived it.

i didn't tweak my kernel, i just use home compiled GENERIC without overriden CFLAGS. everything is almost default install. what about adding a forkbomb in regression tests ?
>How-To-Repeat:
echo 'int main() { for(;;) fork(); }' | gcc -x c - && ./a.out
>Fix:
i don't know how to fix it. it looks like a scheduler issue.
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605220736.k4M7aOuk091200>