Date: Thu, 12 Jul 2007 19:15:57 +1000 (EST) From: Bruce Evans <brde@optusnet.com.au> To: Brian Chu <soc@hbar.us> Cc: bugs@freebsd.org, fs@freebsd.org Subject: Re: msdosfs not MPSAFE Message-ID: <20070712185224.I4682@delplex.bde.org> In-Reply-To: <47a4f3080707111944u2b9ad091t2f4b8be482ab3a69@mail.gmail.com> References: <20070710233455.O2101@besplex.bde.org> <47a4f3080707111944u2b9ad091t2f4b8be482ab3a69@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 11 Jul 2007, Brian Chu wrote: > I've already planned to look at this. I had not been aware that calls > to the Giant Lock were being ignored in the current kernel. Maybe the problem doesn't affect -current. I first saw this bug in a 3-year old version of -current and thought that I verified that it still affects -current. In the old version, getdirentries() and stat() are Giant-locked (not MSTD in syscalls.master), so I don't understand why there was a problem. In -current, msdosfs is not MNTK_MPSAFE, so the problem shouldn't affect -current -- it is already fixed unbetter by Giant-locking everything. [context lost to top posting] Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070712185224.I4682>