Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Aug 2011 01:20:01 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Brandon Gooch <jamesbrandongooch@gmail.com>
Cc:        freebsd-hackers@freebsd.org, Charlie Martin <crmartin@sgi.com>
Subject:   Re: Where to ask about a 7.2 bug, and debugging sys/queue.h errors
Message-ID:  <20110825222001.GX17489@deviant.kiev.zoral.com.ua>
In-Reply-To: <CALBk6yL=T5nfL3rqJtskNS3ahafr0PM-4j5hpqzk8WkK_UXJNQ@mail.gmail.com>
References:  <4E56BB99.6030706@sgi.com> <20110825215348.GW17489@deviant.kiev.zoral.com.ua> <CALBk6yL=T5nfL3rqJtskNS3ahafr0PM-4j5hpqzk8WkK_UXJNQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
On Thu, Aug 25, 2011 at 05:12:09PM -0500, Brandon Gooch wrote:
> On Thu, Aug 25, 2011 at 4:53 PM, Kostik Belousov <kostikbel@gmail.com> wrote:
> > On Thu, Aug 25, 2011 at 03:16:09PM -0600, Charlie Martin wrote:
> >> We're having a crash in some internal code running on FreeBSD 7.2
> >> (specifically š7.2-PRERELEASE FreeBSD 7.2-PRERELEASE and yeah, I know
> >> it's quite a bit behind) in which after 18-30 hours of running load
> >> tests, the code panics with:
> >>
> >> panic: Bad link elm 0xffffff0044c09600 next->prev != elm
> >> cpuid = 0
> >> KDB: stack backtrace:
> >> db_trace_self_wrapper() at 0xffffffff8019119a = db_trace_self_wrapper+0x2a
> >> panic() at 0xffffffff80307c72 = panic+0x182
> >> devfs_populate_loop() at 0xffffffff802a43a8 = devfs_populate_loop+0x548
> >>
> >>
> >> First question: where's the most appropriate place to ask about this
> >> kind of bug on a back version.
> > It is fine to ask there.
> >
> >>
> >> Second: does this remind anyone of any bugs? šGoogling came up with a
> >> few somewhat similar things but hasn't provided much insight so far.
> > In 99% of the cases, it means that you forgot to dev_ref() some cdev.
> 
> So dev_ref increments the reference count for a cdev. Even though the
> work "loop" seems to indicate that we will iterate over a list of
> objects (one of which we may be missing a reference to via a missing
> dev_ref()), I'm not seeing how this can cause a panic from inside
> devfs_populate_loop().
> 
> Can you help me understand this?
> 
Missing dev_ref() means that the memory for the cdev (and cdev_priv) is
freed prematurely. If this happens before destroy_dev() is called,
then the list which is iterated over by populate_loop(), is corrupted.

See e.g. MAKEDEV_REF flag for make_dev(9) and its use in the (old) clone
handlers.

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)

iEYEARECAAYFAk5WypAACgkQC3+MBN1Mb4iO+ACdFJkL5BsS9uhMRInBVw0Mkj/G
0I0An0CAfxULXF/hEhf1aYsFjVul8mMF
=d2bd
-----END PGP SIGNATURE-----

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110825222001.GX17489>