From: "young dave" <hidave.darkstar@gmail.com>
To: "Christoph Lameter" <clameter@sgi.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.22-rc3-mm1 remove bluetooth usb adapter caused kmalloc bug
Date: Wed, 6 Jun 2007 05:55:56 +0000 [thread overview]
Message-ID: <a8e1da0706052255sa487d5ck1724c5a07620a88b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706052211500.7930@schroedinger.engr.sgi.com>
Hi,
>2007/6/6, Christoph Lameter <clameter@sgi.com>:
> Note that the corruption seems to have its cause in a decrement done at
> offset 16 into the object pointing to the refcount in struct hci_dev. So
> it looks like the refcount was decremented after the object was freed.
>
> sysfs related?
>
I noticed in hci_core.c:
hci_dev_close call hci_dev_do_close , then call hci_dev_put
but in hci_dev_do_close also call hci_dev_put
Maybe this is the reason, by apply the below patch the bug seems
doesn't exist, but the strange thing is the 2.4.22-rc4 seems works, I
will test once more to see the result.
Signed-off-by: dave young <hidave.darkstar@gmail.com>
---
net/bluetooth/hci_core.c | 1 -
1 file changed, 1 deletion(-)
diff -dur linux/net/bluetooth/hci_core.c linux.new/net/bluetooth/hci_core.c
--- linux/net/bluetooth/hci_core.c 2007-06-06 13:47:14.000000000 +0000
+++ linux.new/net/bluetooth/hci_core.c 2007-06-06 13:46:58.000000000 +0000
@@ -577,7 +577,6 @@
hci_req_unlock(hdev);
- hci_dev_put(hdev);
return 0;
}
Regards
dave
next prev parent reply other threads:[~2007-06-06 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 1:56 young dave
2007-06-06 2:42 ` Andrew Morton
2007-06-06 2:51 ` young dave
2007-06-06 3:27 ` young dave
2007-06-06 4:30 ` Andrew Morton
2007-06-06 6:55 ` Jiri Kosina
2007-06-06 5:15 ` Christoph Lameter
2007-06-06 5:55 ` young dave [this message]
2007-06-06 7:18 ` dave young
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=a8e1da0706052255sa487d5ck1724c5a07620a88b@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®