From: Marcel Holtmann <marcel@holtmann.org>
To: Andreas Gaufer <andreas.gaufer@blue-cell-networks.com>
Cc: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] Deleted acl-handles on failed hci_create_connection
Date: Thu, 10 Jun 2004 20:53:02 +0200 [thread overview]
Message-ID: <1086893582.7930.55.camel@pegasus> (raw)
In-Reply-To: <20040610203555.273c77bd.Andreas.Gaufer@blue-cell-networks.com>
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
Hi Andreas,
> Heres a patch for hci_event.c to fix the problem that acl-handles are removed
> from the kernels connection hash when a hci_create_connection returnes a
> command status thats not 0x00.
>
> One of the problems that was caused by this bug was that cc could be issued
> even if the peer was already connected. This case leads to the error message
> "Too many links" with sdptool and rfcomm for example. This connection could
> only be removed if the acl handle was known otherwise or by removing power
> from the usb-dongle (unplugg).
I think your patch is wrong, because in case of the first try through
L2CAP etc. a negative return value must result in a drop of the hci_conn
structure. Check if the attached patch is also working (againt 2.6).
Regards
Marcel
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 411 bytes --]
===== net/bluetooth/hci_event.c 1.13 vs edited =====
--- 1.13/net/bluetooth/hci_event.c 2004-05-31 22:15:12 +02:00
+++ edited/net/bluetooth/hci_event.c 2004-06-10 20:48:55 +02:00
@@ -358,7 +358,7 @@
status, batostr(&cp->bdaddr), conn);
if (status) {
- if (conn) {
+ if (conn && conn->state == BT_CONNECT) {
conn->state = BT_CLOSED;
hci_proto_connect_cfm(conn, status);
hci_conn_del(conn);
next prev parent reply other threads:[~2004-06-10 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 18:35 [Bluez-devel] [PATCH] Deleted acl-handles on failed hci_create_connection Andreas Gaufer
2004-06-10 18:53 ` Marcel Holtmann [this message]
2004-06-10 20:29 ` Andreas Gaufer
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=1086893582.7930.55.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andreas.gaufer@blue-cell-networks.com \
--cc=bluez-devel@lists.sourceforge.net \
/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