From: Andrew Morton <akpm@osdl.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
marcel@holtmann.org, maxk@qualcomm.com,
bluez-devel@lists.sourceforge.net
Subject: Re: bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1)
Date: Sat, 23 Dec 2006 17:18:04 -0800 [thread overview]
Message-ID: <20061223171804.e2c22a67.akpm@osdl.org> (raw)
In-Reply-To: <20061223235501.GA1740@elf.ucw.cz>
On Sun, 24 Dec 2006 00:55:01 +0100
Pavel Machek <pavel@ucw.cz> wrote:
> PM: Removing info for No Bus:usbdev3.15_ep81
> PM: Removing info for No Bus:usbdev3.15_ep82
> PM: Removing info for No Bus:usbdev3.15_ep02
> slab error in verify_redzone_free(): cache `size-512': memory outside object was overwritten
> [<c016a1b8>] cache_free_debugcheck+0x128/0x1d0
> [<c04b58e3>] hci_usb_close+0xf3/0x160
> [<c016b530>] kfree+0x50/0xa0
> [<c04b58e3>] hci_usb_close+0xf3/0x160
> [<c04b59be>] hci_usb_disconnect+0x2e/0x90
> [<c0454f23>] usb_disable_interface+0x53/0x70
> [<c04576f8>] usb_unbind_interface+0x38/0x80
> [<c032f908>] __device_release_driver+0x68/0xb0
> [<c032fc3e>] device_release_driver+0x1e/0x40
> [<c032f1db>] bus_remove_device+0x8b/0xa0
> [<c032dbc9>] device_del+0x159/0x1c0
> [<c04559ad>] usb_disable_device+0x4d/0x100
> [<c044fe8a>] usb_disconnect+0x9a/0x110
> [<c0452405>] hub_thread+0x355/0xbd0
> [<c061426e>] schedule+0x2de/0x8f0
> [<c013c640>] autoremove_wake_function+0x0/0x50
> [<c04520b0>] hub_thread+0x0/0xbd0
> [<c013c58c>] kthread+0xec/0xf0
> [<c013c4a0>] kthread+0x0/0xf0
> [<c0103be7>] kernel_thread_helper+0x7/0x10
> =======================
yes, this one looks like memory scribblage in bluetooth. The
buffer.c assertion failure should now be fixed, please verify.
next prev parent reply other threads:[~2006-12-24 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061223234305.GA1809@elf.ucw.cz>
2006-12-24 1:12 ` ext3-related crash in 2.6.20-rc1 Andrew Morton
[not found] ` <20061223235501.GA1740@elf.ucw.cz>
2006-12-24 1:18 ` Andrew Morton [this message]
2006-12-24 23:24 ` bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Pavel Machek
[not found] ` <20061224000150.GA1812@elf.ucw.cz>
[not found] ` <20061224000605.GA1768@elf.ucw.cz>
[not found] ` <20061224000753.GA1811@elf.ucw.cz>
[not found] ` <458DD459.2030209@gmail.com>
[not found] ` <458E69CB.6000107@gmail.com>
2006-12-24 12:22 ` ptrace() memory corruption? Andrew Morton
2006-12-24 13:44 ` Jiri Slaby
2006-12-24 14:39 ` [Bluez-devel] bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Marcel Holtmann
2006-12-24 23:36 ` Pavel Machek
[not found] ` <20061224234357.GA1817@elf.ucw.cz>
[not found] ` <20061228084251.GB3955@ucw.cz>
2006-12-28 10:40 ` Marcel Holtmann
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=20061223171804.e2c22a67.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
--cc=pavel@ucw.cz \
/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