Date: Tue, 27 Mar 2007 13:50:11 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Marcel Moolenaar <xcllnt@mac.com> Cc: cvs-src@FreeBSD.org, Marcel Moolenaar <marcel@FreeBSD.org>, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: cvs commit: src/sys/kern vfs_subr.c Message-ID: <20070327175011.GA82191@xor.obsecurity.org> In-Reply-To: <2EA36547-0EB1-47B0-8F07-D394394CF3BD@mac.com> References: <200703270529.l2R5TfVk087238@repoman.freebsd.org> <20070327074334.GA52121@xor.obsecurity.org> <2EA36547-0EB1-47B0-8F07-D394394CF3BD@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 27, 2007 at 09:36:56AM -0700, Marcel Moolenaar wrote: > > On Mar 27, 2007, at 12:43 AM, Kris Kennaway wrote: > > >On Tue, Mar 27, 2007 at 05:29:41AM +0000, Marcel Moolenaar wrote: > >>marcel 2007-03-27 05:29:41 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: > >> sys/kern vfs_subr.c > >> Log: > >> PowerPC is the only architecture with mpsafe_vfs=0. This is now > >> broken. Rudimentary tests show that PowerPC can run with > >> mpsafe_vfs=1. Make it so... > > > >If this is the vget panic via soft updates then a fix is pending for > >that. Nevertheless mpsafevfs=1 is a good thing :) > > Maybe. I don't have the backtrace handy. It had to do with S/U, so it > probably is then. I didn't see it on my amd64 box, so I assumed it was > specific to PowerPC. Setting mpsave_vfs=1 solved it for me (or > should I say avoided it for me? :-) I figured it's better to hunt down > bugs in the mpsafe_vfs=1 case then it is in the mpsafe_vfs=0 case. > This is not to say that mpsafe_vfs=0 can be broken, but rather that > I prefer to work on improving the mpsafe_vfs=1 case... I agree that this is preferable. thanks, Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070327175011.GA82191>