Date: Tue, 8 Oct 2002 12:28:17 -0700 (PDT) From: "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> To: Jeff Roberson <jroberson@chesapeake.net> Cc: "Brian F. Feldman" <green@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: panic from _mutex_assert in kern_lock.c Message-ID: <200210081928.g98JSHJ0039964@troutmask.apl.washington.edu> In-Reply-To: <20021008152323.F75846-100000@mail.chesapeake.net> "from Jeff Roberson at Oct 8, 2002 03:24:04 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Jeff Roberson said:
>
> On Sat, 5 Oct 2002, Brian F. Feldman wrote:
>
>> "Steven G. Kargl" <kargl@troutmask.apl.washington.edu> wrote:
>>> The source tree was retrieved by cvsup
>>> at 21:47 (PST) on Oct 4.
>>>
>>> This is a non-GEOM and non-acpi kernel.
>>>
>>> I have the core and kernel.debug, so any
>>> further postmortem is possible.
>>
>> I think the problem is that in src/sys/ufs/ffs/
>> ffs_snapshot.c:ffs_snapshot(),
>> as the mnt vnode list is traversed none of the vnodes ("xvp") would
>> actually GET VI_LOCK()ed in the first place, and so the LK_INTERLOCK
>> is bogus in the vn_lock() call. Kirk would know for sure what to do
>> about this...
>>
>
> Yeah, I broke this. I didn't see the LK_INTERLOCK near by when I removed
> the interlocking around usecount. I will fix this.
>
I sent Kirk a private email, but I haven't heard back from him.
Hopefully, he is watching the freebsd-current mailing list.
I'm actually surprise that more people haven't reported this problem.
--
Steve
http://troutmask.apl.washington.edu/~kargl/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210081928.g98JSHJ0039964>