Bug 18842 - BUG kmalloc-512: Poison overwritten when running with debug enabled
Summary: BUG kmalloc-512: Poison overwritten when running with debug enabled
Status: RESOLVED OBSOLETE
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Arnaldo Carvalho de Melo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-20 15:25 UTC by Alex Villacis Lasso
Modified: 2012-08-13 16:38 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.36-rc4
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg output with backtrace at the end (123.87 KB, text/plain)
2010-09-20 15:25 UTC, Alex Villacis Lasso 		Details
Kernel configuration used to compile crashing kernel (97.52 KB, text/plain)
2010-09-20 15:28 UTC, Alex Villacis Lasso 		Details
Further dmesg with backtrace (123.46 KB, text/plain)
2010-09-20 20:48 UTC, Alex Villacis Lasso 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Alex Villacis Lasso 2010-09-20 15:25:00 UTC 
Created attachment 30752 [details]
dmesg output with backtrace at the end

Description:

I am running with several kernel debugging options enabled, in order to track possible causes of https://bugs.freedesktop.org/show_bug.cgi?id=29325 . During this run, while leaving a Bittorrent client running over the weekend, I found the attached backtrace in the kernel log on Monday.

To reproduce (speculative):
- Enable debugging options as indicated by attached config
- Leave moderate network activity (Bittorrent) running for a few days

Actual results:
Backtrace found on dmesg. System seems to run normally.

Expected results:
No backtrace.

Kernel built on Sep. 17 2010 on Fedora 12 x86_64
Comment 1 Alex Villacis Lasso 2010-09-20 15:28:29 UTC 
Created attachment 30762 [details]
Kernel configuration used to compile crashing kernel
Comment 2 Alex Villacis Lasso 2010-09-20 20:48:30 UTC 
Created attachment 30832 [details]
Further dmesg with backtrace

This second backtrace is in the same session as the first one. I started Azureus (the Bittorrent client) a few times before I noticed this second backtrace, but I could not confirm whether starting Azureus actually *causes* the backtrace.
Comment 3 Alex Villacis Lasso 2010-09-22 17:46:46 UTC 
Now testing for the bug with commit 8b15575cae7a93a784c3005c42b069edd9ba64dd past 2.6.36-rc5 in mainline kernel...
Note You need to log in before you can comment on or make changes to this bug.