Date: Wed, 18 Aug 2004 13:18:40 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: Robert Watson <rwatson@FreeBSD.org> Cc: Current <freebsd-current@FreeBSD.org> Subject: Re: panic: lock (sleep mutex) inp not locked @ /usr/src/sys/netinet6/in6_pcb.c:710 Message-ID: <7mwtzxaxjz.wl@black.imgsrc.co.jp> In-Reply-To: <Pine.NEB.3.96L.1040817234556.28987M-100000@fledge.watson.org> References: <7m7jrxcmen.wl@black.imgsrc.co.jp> <Pine.NEB.3.96L.1040817234556.28987M-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At Wed, 18 Aug 2004 00:02:44 -0400 (EDT),
Robert Watson wrote:
> Hmm. This code is somewhat more spaghetti than I thought. In the IPv4
> version, we check the return value of the notify function to decide if we
> need to unlock. Something like the following may fix this:
Okay, I'll try with your patch.
> Do you have a dump for this? If so, is there any chance you could tell me
> what function 'notify' was set to point to, and what the value of 'inp' is
> there?
Sorry, I didn't take a dump at this time. I'll take it when I get a
panic next time.
> in6_pcbnotify(c0709d40,e4d3abb0,1600,e4d3abd0,9bed) at in6_pcbnotify+0x26d
Is "9bed" is the value of notify argument? It seems it is too small
for function pointer...
--
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mwtzxaxjz.wl>