Date: Sun, 24 Sep 2006 18:53:20 GMT From: Bruce M Simpson <bms@FreeBSD.org> To: bernd@uebi.net, bms@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/94446: FreeBSD 6.0 crash with forkbomb (regression) Message-ID: <200609241853.k8OIrKa5092036@freefall.freebsd.org>
index | next in thread | raw e-mail
Synopsis: FreeBSD 6.0 crash with forkbomb (regression) State-Changed-From-To: open->feedback State-Changed-By: bms State-Changed-When: Sun Sep 24 18:47:04 UTC 2006 State-Changed-Why: This report is quite confusing -- without more evidence it's difficult to have something to go on. I can reproduce a panic in -CURRENT with forkbomb as the submitter describes, but it looks like a diagnostic; running forkbomb as a non-root user doesn't panic the machine due to the proces limit. The panic is pretty much as I'd expect. It would be good to harden things a bit more along this path, but from reading CVS history for these files it looks as though the behaviour was changed to avoid a lock-order reversal. http://www.freebsd.org/cgi/query-pr.cgi?pr=94446home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200609241853.k8OIrKa5092036>
