Date: Sat, 25 Aug 2007 22:37:54 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-current@freebsd.org, tegge@freebsd.org Subject: Re: insmntque for syncvnode panic [Was: Re: panic unmounting filesystems] Message-ID: <20070825123754.GM17244@turion.vk2pj.dyndns.org> In-Reply-To: <20070821144303.GD2738@deviant.kiev.zoral.com.ua> References: <20070817073321.GA6321@turion.vk2pj.dyndns.org> <20070821144303.GD2738@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
--M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Aug-21 17:43:03 +0300, Kostik Belousov <kostikbel@gmail.com> wrote: >> The mountpoint shows as in the process of being unmounted and has >> mnt_nvnodelistsize =3D=3D 0 so insmntque() makes sense at the micro leve= l. >> Having a system panic as a result does not make sense. >Sure. I think that syncvnode shall be allocated after the MNTK_UNMOUNT >flag is cleared. > >Could you, please, test the patch below ? >diff --git a/sys/kern/vfs_mount.c b/sys/kern/vfs_mount.c >index 702efc3..09f4d1e 100644 This appears to have resolved the problem - after adding the patch, I've been unable to get umount to panic. Thanks for the fix. --=20 Peter Jeremy --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFG0CKi/opHv/APuIcRArufAJ90mcntnnYsCGZJp/+25kf2PoTjdACfWka4 s3+yM9g6hYlfC7eSkZeleFY= =z5Ih -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070825123754.GM17244>