Re: Re: Slab corruption after unloading a module

From: Zhiyi Huang
Date: Wed Apr 12 2006 - 00:08:56 EST


>
> From: "Hareesh Nagarajan" <hnagar2@xxxxxxxxx>
> Date: 2006/04/12 Wed PM 03:51:22 GMT+12:00
> To: hzy@xxxxxxxxxxxxxx
> CC: linux-kernel@xxxxxxxxxxxxxxx, zhiyi6@xxxxxxxxxx
> Subject: Re: Slab corruption after unloading a module
>
> Why don't you compile the kernel with CONFIG_DEBUG_SLAB=y and see
what the
> debug messages have to say?

Thanks for help. I already configured the kernel with CONFIG_DEBUG_SLAB=y,
but I changed the current log level from 7 to 8. I got similar messages below.
I still have no clue. The messages show nothing about my module. Any more
suggestions?

Hello world from Template Module
temp device MAJOR is 252
Good bye from Template Module: 618 pages
Slab corruption: start=c7933c38, len=192
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c01ac52d>](load_elf_interp+0xdd/0x2d0)
070: 6b 6b 6b 6b ac 3c 93 c7 ac 3c 93 c7 6b 6b 6b 6b
Prev obj: start=c7933b6c, 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
Next obj: start=c7933d04, len=192
Redzone: 0x5a2cf071/0x5a2cf071.
Last user: [<c01e58fa>](__journal_remove_checkpoint+0x4a/0xa0)
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/