Date: Mon, 18 Feb 2008 19:21:55 +0100 From: Volker <volker@vwsoft.com> To: Wesley Shields <wxs@FreeBSD.org> Cc: Peter Sanchez <petersanchez@gmail.com>, freebsd-security@freebsd.org Subject: Re: How to take down a system to the point of requiring a newfs with one line of C (userland) Message-ID: <47B9CCC3.9060203@vwsoft.com> In-Reply-To: <20080218180441.GE14660@atarininja.org> References: <a9f4a3860802180527k6fcfbdaeuf235540075b263b5@mail.gmail.com> <200802181414.m1IEE8bd075081@drugs.dv.isc.org> <20080218150748.GD90004@atarininja.org> <268BFF3D-3853-40D5-9D69-6FC876E07ABB@gmail.com> <20080218180441.GE14660@atarininja.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/18/08 19:04, Wesley Shields wrote: > On Mon, Feb 18, 2008 at 09:25:29AM -0800, Peter Sanchez wrote: >> On Feb 18, 2008, at 7:07 AM, Wesley Shields wrote: >>> I tried this using /tmp/ as argv[1] and it didn't crash a 6.2 machine or >>> a -current from a few weeks ago. Maybe the number of files has to be >>> increased? I bumped it up to 100000 and tried on a 6.2 machine, but I >>> ran out of inodes before I could induce a crash. :) >>> >>> Maybe I'm doing something wrong? >> I believe the panic doesn't occur until boot. Did you reboot the box after >> writing the files to /tmp? >> >> Peter > > I did on a 6.2 machine with 10000 files in /tmp. I can reboot the > -current machine later tonight if you think it will make a difference. According to the problem report, it should panic while mounting the fs. umount and re-mount /tmp and see, if you can make it panic (a reboot shouldn't be necessary here). If you're able to do so, please send in a complete panic message and backtrace - if possible, please!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47B9CCC3.9060203>