Date: Tue, 4 Mar 1997 16:16:46 +1030 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jlemon@americantv.com (Jonathan Lemon) Cc: hackers@freebsd.org, msmith@atrad.adelaide.edu.au Subject: Re: xemacs crashes kernel Message-ID: <199703040546.QAA10965@genesis.atrad.adelaide.edu.au> In-Reply-To: <19970303233743.01587@right.PCS> from Jonathan Lemon at "Mar 3, 97 11:37:43 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Lemon stands accused of saying: > On Mar 03, 1997 at 11:01:57PM -0600, Jonathan Lemon wrote: > > > > stopped at _fsync+0x73, testb $0x40, 0x18(%eax) > > Just to follow up on the really obvious, this failure is in fsync(), at: > > error = VOP_FSYNC(vp, fp->f_cred, > (vp->v_mount->mnt_flag & MNT_ASYNC) ? MNT_NOWAIT : MNT_WAIT, p); > > where 0x40 is MNT_ASYNC, and %eax is supposed to contain vp->v_mount, but > contains a NULL pointer instead. Since this is filesystem related, I should > mention that I have both MFS and PROCFS in the kernel, and that MFS is > mounted on /tmp (async, local). (if this makes any difference) The MFS code doesn't appear to touch v_mount at all. By contrast, the UFS code does, but it appears to only read it. If you don't mount /tmp on your MFS, does the system still barf? > Jonathan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703040546.QAA10965>