Maxime Henrion wrote: > > Maxim Sobolev wrote: > > Any ideas? > > Looks like some other processes was modifying the mountlist while > vfs_unmountall() was running. Is this an SMP box ?
No, it's UP. > It would be nice if > you could check in gdb which other process was holding the mountlist_mtx > mutex if any. Sure, if you will provide me with instruction on how to do in. > The vfs_unmountall() function doesn't acquire the > mounstlist_mtx and states this is OK in a comment because this functions > is ran upon reboot, but I suspect this is incorrect and we still need to > do the locking. I'll write a patch tonight to add locking into > vfs_unmountall(), but it may be hard to test unless you know of a way to > reproduce this panic easily. No, I don't. It's the first time I've encountered this particular problem. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
