From: Marcel Holtmann <marcel@holtmann.org>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [Bluez-devel] Re: [BUG] BlueTooth socket busted in 2.6.0-test5
Date: 11 Sep 2003 01:39:28 +0200 [thread overview]
Message-ID: <1063237174.28890.6.camel@pegasus> (raw)
In-Reply-To: <20030910225810.GA7712@bougret.hpl.hp.com>
Hi Jean,
> This is self explanatory :
> -----------------------------------------------------------
> kernel BUG at include/net/sock.h:459!
> invalid operand: 0000 [#1]
> CPU: 1
> EIP: 0060:[<d08ae64e>] Not tainted
> EFLAGS: 00010282
> EIP is at l2cap_sock_alloc+0x36/0xb4 [l2cap]
> eax: d08b3500 ebx: c6b4de40 ecx: 00000020 edx: d08ac440
> esi: 00000000 edi: 00000000 ebp: ffffffa3 esp: c81abf1c
> ds: 007b es: 007b ss: 0068
> Process sdpd (pid: 390, threadinfo=c81aa000 task=ce634cc0)
> Stack: 00000000 d08ac524 d08ae72c c20e7780 00000000 000000d0 d08a10f4 c20e7780
> 00000000 c20e7780 0000007c c033ecc0 ffffff9f c01e1236 c20e7780 00000000
> 0000001f bffff894 c81abfa8 00000001 c01e1325 0000001f 00000005 00000000
> Call Trace:
> [<d08ae72c>] l2cap_sock_create+0x60/0x7c [l2cap]
> [<d08a10f4>] bt_sock_create+0x8c/0xd0 [bluetooth]
> [<c01e1236>] sock_create+0x12e/0x200
> [<c01e1325>] sys_socket+0x1d/0x50
> [<c01e216c>] sys_socketcall+0xbc/0x260
> [<c0108cd3>] syscall_call+0x7/0xb
>
> Code: 0f 0b cb 01 e2 1a 8b d0 89 83 28 01 00 00 85 c0 74 30 50 e8
>
> -----------------------------------------------------------
>
> Basically, the socket is already owned by the 'bluetooth'
> module in bt_sock_alloc(), and the 'l2cap' module try to change the
> ownersip to itself in l2cap_sock_alloc(). The socket layer doesn't
> like it. At least, that's the way I read it.
> Without the ability to open BT socket, BT is pretty much
> useless.
yesterday David Woodhouse sent a patch which should fix this.
Regards
Marcel
===== net/bluetooth/af_bluetooth.c 1.22 vs edited =====
--- 1.22/net/bluetooth/af_bluetooth.c Sun Aug 31 03:30:42 2003
+++ edited/net/bluetooth/af_bluetooth.c Tue Sep 9 11:28:51 2003
@@ -130,7 +130,6 @@
}
sock_init_data(sock, sk);
- sk_set_owner(sk, THIS_MODULE);
INIT_LIST_HEAD(&bt_sk(sk)->accept_q);
sk->sk_zapped = 0;
===== net/bluetooth/hci_sock.c 1.24 vs edited =====
--- 1.24/net/bluetooth/hci_sock.c Sat Jul 5 07:52:58 2003
+++ edited/net/bluetooth/hci_sock.c Tue Sep 9 11:30:43 2003
@@ -587,6 +587,8 @@
if (!sk)
return -ENOMEM;
+ sk_set_owner(sk, THIS_MODULE);
+
sock->state = SS_UNCONNECTED;
sk->sk_state = BT_OPEN;
===== net/bluetooth/bnep/sock.c 1.11 vs edited =====
--- 1.11/net/bluetooth/bnep/sock.c Thu Jun 5 01:57:08 2003
+++ edited/net/bluetooth/bnep/sock.c Tue Sep 9 11:29:54 2003
@@ -175,6 +175,9 @@
if (!(sk = bt_sock_alloc(sock, PF_BLUETOOTH, 0, GFP_KERNEL)))
return -ENOMEM;
+
+ sk_set_owner(sk, THIS_MODULE);
+
sock->ops = &bnep_sock_ops;
sock->state = SS_UNCONNECTED;
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
WARNING: multiple messages have this Message-ID (diff)
From: Marcel Holtmann <marcel@holtmann.org>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Max Krasnyansky <maxk@qualcomm.com>,
BlueZ Mailing List <bluez-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] BlueTooth socket busted in 2.6.0-test5
Date: 11 Sep 2003 01:39:28 +0200 [thread overview]
Message-ID: <1063237174.28890.6.camel@pegasus> (raw)
In-Reply-To: <20030910225810.GA7712@bougret.hpl.hp.com>
Hi Jean,
> This is self explanatory :
> -----------------------------------------------------------
> kernel BUG at include/net/sock.h:459!
> invalid operand: 0000 [#1]
> CPU: 1
> EIP: 0060:[<d08ae64e>] Not tainted
> EFLAGS: 00010282
> EIP is at l2cap_sock_alloc+0x36/0xb4 [l2cap]
> eax: d08b3500 ebx: c6b4de40 ecx: 00000020 edx: d08ac440
> esi: 00000000 edi: 00000000 ebp: ffffffa3 esp: c81abf1c
> ds: 007b es: 007b ss: 0068
> Process sdpd (pid: 390, threadinfo=c81aa000 task=ce634cc0)
> Stack: 00000000 d08ac524 d08ae72c c20e7780 00000000 000000d0 d08a10f4 c20e7780
> 00000000 c20e7780 0000007c c033ecc0 ffffff9f c01e1236 c20e7780 00000000
> 0000001f bffff894 c81abfa8 00000001 c01e1325 0000001f 00000005 00000000
> Call Trace:
> [<d08ae72c>] l2cap_sock_create+0x60/0x7c [l2cap]
> [<d08a10f4>] bt_sock_create+0x8c/0xd0 [bluetooth]
> [<c01e1236>] sock_create+0x12e/0x200
> [<c01e1325>] sys_socket+0x1d/0x50
> [<c01e216c>] sys_socketcall+0xbc/0x260
> [<c0108cd3>] syscall_call+0x7/0xb
>
> Code: 0f 0b cb 01 e2 1a 8b d0 89 83 28 01 00 00 85 c0 74 30 50 e8
>
> -----------------------------------------------------------
>
> Basically, the socket is already owned by the 'bluetooth'
> module in bt_sock_alloc(), and the 'l2cap' module try to change the
> ownersip to itself in l2cap_sock_alloc(). The socket layer doesn't
> like it. At least, that's the way I read it.
> Without the ability to open BT socket, BT is pretty much
> useless.
yesterday David Woodhouse sent a patch which should fix this.
Regards
Marcel
===== net/bluetooth/af_bluetooth.c 1.22 vs edited =====
--- 1.22/net/bluetooth/af_bluetooth.c Sun Aug 31 03:30:42 2003
+++ edited/net/bluetooth/af_bluetooth.c Tue Sep 9 11:28:51 2003
@@ -130,7 +130,6 @@
}
sock_init_data(sock, sk);
- sk_set_owner(sk, THIS_MODULE);
INIT_LIST_HEAD(&bt_sk(sk)->accept_q);
sk->sk_zapped = 0;
===== net/bluetooth/hci_sock.c 1.24 vs edited =====
--- 1.24/net/bluetooth/hci_sock.c Sat Jul 5 07:52:58 2003
+++ edited/net/bluetooth/hci_sock.c Tue Sep 9 11:30:43 2003
@@ -587,6 +587,8 @@
if (!sk)
return -ENOMEM;
+ sk_set_owner(sk, THIS_MODULE);
+
sock->state = SS_UNCONNECTED;
sk->sk_state = BT_OPEN;
===== net/bluetooth/bnep/sock.c 1.11 vs edited =====
--- 1.11/net/bluetooth/bnep/sock.c Thu Jun 5 01:57:08 2003
+++ edited/net/bluetooth/bnep/sock.c Tue Sep 9 11:29:54 2003
@@ -175,6 +175,9 @@
if (!(sk = bt_sock_alloc(sock, PF_BLUETOOTH, 0, GFP_KERNEL)))
return -ENOMEM;
+
+ sk_set_owner(sk, THIS_MODULE);
+
sock->ops = &bnep_sock_ops;
sock->state = SS_UNCONNECTED;
next prev parent reply other threads:[~2003-09-10 23:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-10 22:58 [BUG] BlueTooth socket busted in 2.6.0-test5 Jean Tourrilhes
2003-09-10 23:39 ` Marcel Holtmann [this message]
2003-09-10 23:39 ` Marcel Holtmann
2003-09-10 23:47 ` Jean Tourrilhes
2003-09-11 20:32 ` Jean Tourrilhes
2003-09-12 5:21 ` [Bluez-devel] " David Woodhouse
2003-09-12 8:19 ` David Woodhouse
2003-09-12 21:34 ` Jean Tourrilhes
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=1063237174.28890.6.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.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 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.