From: Marcel Holtmann <marcel@holtmann.org>
To: Eugene Crosser <crosser@average.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 14:22:35 +0100 [thread overview]
Message-ID: <1073913755.3126.48.camel@pegasus> (raw)
In-Reply-To: <1073889186.3923.27.camel@pccross.average.org>
Hi Eugene,
> 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.
it is ok that the L2CAP refcount is increased, because every RFCOMM
connection needs an underlaying L2CAP link. But of course the increase
and the decrease should be the same ;)
> 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?
Let us summarize this problem a little bit. We know that this is
refcount bug and it happens in __module_get(). It also seems that we
only get hit by this bug if we got in incoming connection. Is this
right? Do the refcounting work correct on outgoing? My question is if
this is a L2CAP only problem or if it only happens in conjunction with
RFCOMM? Can you reproduce it with the l2test program only? Don't load
the rfcomm.ko module and don't start the sdpd, so you have a better
starting refcount.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-01-12 13:22 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
2004-01-12 13:22 ` Marcel Holtmann [this message]
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=1073913755.3126.48.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=crosser@average.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.