From: Johan Hedberg <johan.hedberg@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Bluetoothd crashing on 4.7
Date: Sun, 28 Sep 2008 00:12:56 +0300 [thread overview]
Message-ID: <3B81408E-617A-46F5-A8D2-89C70E4E97FD@gmail.com> (raw)
In-Reply-To: <48DD699C.9090307@dell.com>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Hi Mario,
On Sep 27, 2008, at 2:00, Mario Limonciello wrote:
> I recently packaged bluez 4.7 for possible inclusion in Ubuntu
> intrepid
> [1]. Upon doing some basic testing with it, I've run into a situation
> where when I try to pair with a keyboard, bluetoothd crashes. If I
> run
> it under valgrind, bluetoothd survives the crash, and the keyboard
> works
> [2]. If I run it with gdb, it comes down, and I get a trace at
> least[3]. If I run it without a debugger, keyboard doesn't properly
> work.
This is probably caused by my cleanup/rewrite patches for the pairing
logic in 4.7. Based on the gdb trace the attached patch should fix the
issue. It's also pushed to the kernel.org git and should appear in the
next release.
Johan
[-- Attachment #2: bluetoothd-segfault.patch --]
[-- Type: application/octet-stream, Size: 568 bytes --]
commit cccde44377fc5bb5d9db51ca6b4fcb790c7d24ba
Author: Johan Hedberg <johan.hedberg@nokia.com>
Date: Sat Sep 27 14:08:42 2008 -0700
Fix potential NULL pointer dereference
diff --git a/src/dbus-hci.c b/src/dbus-hci.c
index 795df0a..eea166e 100644
--- a/src/dbus-hci.c
+++ b/src/dbus-hci.c
@@ -518,7 +518,7 @@ void hcid_dbus_bonding_process_complete(bdaddr_t *local, bdaddr_t *peer,
bonding = adapter_get_bonding_info(adapter);
- if (bacmp(&bonding->bdaddr, peer))
+ if (bonding && bacmp(&bonding->bdaddr, peer))
bonding = NULL;
if (status == 0) {
[-- Attachment #3: Type: text/plain, Size: 1 bytes --]
prev parent reply other threads:[~2008-09-27 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 23:00 Bluetoothd crashing on 4.7 Mario Limonciello
2008-09-26 23:36 ` Mario Limonciello
2008-09-27 21:12 ` Johan Hedberg [this message]
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=3B81408E-617A-46F5-A8D2-89C70E4E97FD@gmail.com \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox