insmntque for syncvnode panic [Was: Re: panic unmounting filesystems]

Peter Jeremy peterjeremy at optushome.com.au
Sat Aug 25 05:37:56 PDT 2007


On 2007-Aug-21 17:43:03 +0300, Kostik Belousov <kostikbel at gmail.com> wrote:
>> The mountpoint shows as in the process of being unmounted and has
>> mnt_nvnodelistsize == 0 so insmntque() makes sense at the micro level.
>> 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.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070825/77610480/attachment.pgp


More information about the freebsd-current mailing list