From: Eugene Crosser <crosser@average.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Reproducible kernel oops on PPP session start
Date: Mon, 12 Jan 2004 09:33:06 +0300 [thread overview]
Message-ID: <1073889186.3923.27.camel@pccross.average.org> (raw)
In-Reply-To: <1073833166.3126.24.camel@pegasus>
On Sun, 2004-01-11 at 17:59, Marcel Holtmann wrote:
> > > As far as I can tell from analyzing the dump, and objdump of l2cap.o
> > > object, BUG() happens when "sk_set_owner(sk, THIS_MODULE);" in
> > > net/bluetooth/l2cap.c line 353 encounters zero refcount of the module.
> > > So, probably somebody incorrectly decreases the l2cap's refcount
> > > elsewhere...
> >
> > yes, this seems to be true (and explains the fixed number of attempts).
> > Reference count increases by one every time session starts, and
> > decreases by *two* when it is finished. Why initial refcount is 5 is
> > still unclear to me...
>
> I thought all refcount bugs were fixed, but the initial refcount is easy
> to explain. It should be raised by the RFCOMM module and the sdpd. Try
> to not load RFCOMM and disable the starting of the sdpd.
Interesting that running "rfcomm bind" or "rfcomm listen" does not
increase l2cap's refcount. It gets increased at the moment when
incoming connection actually takes place. And is decreased (by 2) when
it terminates.
I do not understand how refcount is maintained well enough to do further
investigation myself. Anything I can do to help you (or anybody) to fix
the problem?
Eugene
next prev parent reply other threads:[~2004-01-12 6:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 11:42 Reproducible kernel oops on PPP session start Eugene Crosser
2004-01-07 12:15 ` [Bluez-devel] " Marcel Holtmann
2004-01-07 13:57 ` Eugene Crosser
2004-01-10 12:00 ` Eugene Crosser
2004-01-10 12:11 ` Eugene Crosser
2004-01-11 14:59 ` Marcel Holtmann
2004-01-12 6:33 ` Eugene Crosser [this message]
2004-01-12 13:22 ` Marcel Holtmann
2004-01-12 14:52 ` Eugene Crosser
2004-01-12 15:15 ` Marcel Holtmann
2004-01-12 21:22 ` Eugene Crosser
2004-01-12 21:35 ` Marcel Holtmann
2004-01-12 22:02 ` Eugene Crosser
2004-01-13 17:32 ` Marcel Holtmann
2004-01-13 19:33 ` Marcel Holtmann
2004-01-13 21:32 ` Eugene Crosser
2004-01-13 23:14 ` Marcel Holtmann
2004-01-07 14:05 ` Edd Dumbill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1073889186.3923.27.camel@pccross.average.org \
--to=crosser@average.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.