Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ville.tervo@nokia.com
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: rfcomm oops
Date: Mon, 04 Jul 2005 17:29:04 +0200	[thread overview]
Message-ID: <1120490944.10273.164.camel@pegasus> (raw)
In-Reply-To: <1120490370.30194.50.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

Hi Ville,

> I found reproducible way to make rfcomm layer oops. I attached oops and
> some notes how they were produced. I used several Nokia phones and IBM
> T40 laptop in these tests.

if the attached patch makes it go away, then I know what it is. Actually
I introduced that problem when I tried to fix another bug with buggy
phones that can't disconnect their DLCI 0 even if they established it.

Regards

Marcel


[-- Attachment #2: patch --]
[-- Type: text/x-patch, Size: 484 bytes --]

diff --git a/net/bluetooth/rfcomm/core.c b/net/bluetooth/rfcomm/core.c
--- a/net/bluetooth/rfcomm/core.c
+++ b/net/bluetooth/rfcomm/core.c
@@ -389,8 +389,6 @@ static int __rfcomm_dlc_close(struct rfc
 		rfcomm_dlc_unlock(d);
 
 		skb_queue_purge(&d->tx_queue);
-		rfcomm_session_put(s);
-
 		rfcomm_dlc_unlink(d);
 	}
 
@@ -600,8 +598,6 @@ static struct rfcomm_session *rfcomm_ses
 		goto failed;
 	}
 
-	rfcomm_session_hold(s);
-
 	s->initiator = 1;
 
 	bacpy(&addr.l2_bdaddr, dst);

  reply	other threads:[~2005-07-04 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 15:19 rfcomm oops Ville Tervo
2005-07-04 15:29 ` Marcel Holtmann [this message]
2005-07-05  7:41   ` Ville Tervo
2005-07-05  8:14     ` [Bluez-devel] " Marcel Holtmann
2005-07-04 15:37 ` [Bluez-devel] " Wolfram Quester

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=1120490944.10273.164.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=ville.tervo@nokia.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox