Messages in this thread | | | From | Zhiyi Huang <> | Subject | Slab corruption after unloading a module | Date | Wed, 12 Apr 2006 12:37:23 +1200 |
| |
Hi there, I am a bit timid to post a message to the list after reading the FAQ, but I did get a problem. When reply, please cc to my email address. My kernel info: Linux version 2.6.8 (root@zhiyi) (gcc version 3.3.5 (Debian 1:3.3.5-8)) #1 Everytime (except the first time) I unload my module (a ram device), I got the following message. Please just indicate if it is a kernel bug or if there is any fix patch. At the moment I have no clue. I used kmalloc and alloc_page to allocate memory dynamically when the ram device grows. And I freed them when the module is unloaded of course.
Hello world from Template Module temp device MAJOR is 253 Good bye from Template Module: 618 pages Hello world from Template Module temp device MAJOR is 253 Good bye from Template Module: 618 pages Slab corruption: start=c7c12d24, len=192 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<c01ac52d>](load_elf_interp+0xdd/0x2d0) 070: 6b 6b 6b 6b 98 2d c1 c7 98 2d c1 c7 6b 6b 6b 6b Prev obj: start=c7c12c58, len=192 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<c01ac52d>](load_elf_interp+0xdd/0x2d0) 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b Next obj: start=c7c12df0, len=192 Redzone: 0x5a2cf071/0x5a2cf071. Last user: [<00000000>](0x0) 000: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 010: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |