Date: Tue, 9 Aug 2005 18:38:39 +1000 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Nate Lawson <nate@root.org> Cc: cvs-src@freebsd.org, Don Lewis <truckman@freebsd.org>, src-committers@freebsd.org, csjp@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_sysctl.c Message-ID: <20050809083839.GD9970@cirb503493.alcatel.com.au> In-Reply-To: <42F7BA45.4040700@root.org> References: <200508081956.j78Jui1l095716@gw.catspoiler.org> <42F7BA45.4040700@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2005-Aug-08 13:02:13 -0700, Nate Lawson wrote: >Don Lewis wrote: >>On 8 Aug, Christian S.J. Peron wrote: >>> memory. This can result in a number of different locking issues, >>> including dead locks. > >One other thing: I don't think this should be MFCd before 6.0. It's >possible that there are some drivers that violate this rule and having a >release trigger panics is bad. This is the same reason we turn off >INVARIANTS for releases. I personally think panics are preferable to deadlocks. At least with a panic, it's obvious that something went wrong, and you have a fighting chance of finding out why. Having a computer freeze for no apparent reason is extremely frustrating - especially if it does so gradually. If necessary, we can always set the console background to blue and/or call it a "guru meditation message" :-) -- Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050809083839.GD9970>