LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Quel Qun <kelk1@comcast.net>
Cc: Dave Young <hidave.darkstar@gmail.com>,
Marcel Holtmann <marcel@holtmann.org>,
LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Kernel oops with bluetooth usb dongle
Date: Fri, 22 Feb 2008 08:23:06 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0802220813180.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <022220080240.25836.47BE362900072A1C000064EC2200761394CE05040A05@comcast.net>
Quel,
On Fri, 22 Feb 2008, Quel Qun wrote:
> $ addr2line -e vmlinux c012d51d
> /usr/src/linux-2.6.25-rc2-git5kk1/kernel/timer.c:770
>
> Crap, that is on the next list_for_each_entry in timer.c :(
>
> I tried to make a similar test loop as you did a few lines above:
Cool.
> I thought I got it on the next crash, but the system locked too
> fast, and the only thing I saw was:
>
> TTRACE timer f7b52858 fn f8e7c608 addr c012d776
> TTRACE fn l2cap_info_timeout
> TTRACE addr mod_timer
> BUG: unable to handle kernel paging request at 6b6b6b6b
That's what I wanted to see.
> I hope the tiny bit of trace can trigger some idea. At least l2cap
> has something to do with bluetooth. l2cap_info_timeout is line 360
> of net/bluetooth/l2cap.c, apparently only called from
> l2cap_conn_add, line 391: setup_timer(&conn->info_timer,
> l2cap_info_timeout, (unsigned long)conn);
Correct. And I don't see how it's guaranteed that the timer is deleted
before l2cap_conn_del() is called which kfree's the l2cap_conn
structure.
> After four hours and ten crashes today, it is the little I
> got. Kernel stuff is tough...
Yes, it is. The little information you got should be enough to solve
this. Thanks for your patience and help !
Does the patch below fix your problem ?
Thanks,
tglx
---
net/bluetooth/l2cap.c | 2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6/net/bluetooth/l2cap.c
===================================================================
--- linux-2.6.orig/net/bluetooth/l2cap.c
+++ linux-2.6/net/bluetooth/l2cap.c
@@ -417,6 +417,8 @@ static void l2cap_conn_del(struct hci_co
l2cap_sock_kill(sk);
}
+ del_timer(&conn->info_timer);
+
hcon->l2cap_data = NULL;
kfree(conn);
}
next prev parent reply other threads:[~2008-02-22 7:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 2:40 Quel Qun
2008-02-22 3:23 ` Dave Young
2008-02-22 7:23 ` Thomas Gleixner [this message]
2008-02-22 11:34 ` David Woodhouse
2008-02-22 11:43 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2008-02-26 15:49 Quel Qun
2008-02-26 0:03 Quel Qun
2008-02-26 3:13 ` Marcel Holtmann
2008-02-28 1:03 ` Dave Young
2008-02-28 1:37 ` Dave Young
2008-02-21 16:49 Quel Qun
2008-02-21 19:37 ` Thomas Gleixner
2008-02-18 0:01 Quel Qun
2008-02-18 12:43 ` Sebastian Siewior
2008-02-18 13:12 ` Thomas Gleixner
2008-02-19 21:07 ` Marcel Holtmann
2008-02-20 0:14 ` Thomas Gleixner
2008-02-20 8:11 ` Thomas Gleixner
2008-02-21 7:30 ` Dave Young
2008-02-16 21:37 Quel Qun
2008-02-16 23:59 ` Thomas Gleixner
2008-02-16 0:41 Quel Qun
2008-02-16 11:05 ` Jiri Kosina
2008-02-16 11:50 ` Thomas Gleixner
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=alpine.LFD.1.00.0802220813180.7583@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=hidave.darkstar@gmail.com \
--cc=jkosina@suse.cz \
--cc=kelk1@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mingo@elte.hu \
--subject='Re: Kernel oops with bluetooth usb dongle' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).