Re: Slab corruption after unloading a module

["Randy.Dunlap" <rdunlap@xenotime.net>]

On Thu, 13 Apr 2006 11:04:39 +1200 Zhiyi Huang wrote:

> > 2.6.8 is an old kernel, you could very well be hitting a kernel bug
> > that has been fixed already. Can you reproduce this with 2.6.16? 
> 
> I will try that soon.
> 
> > Also,
> > you're not including sources to your module so it's impossible to tell
> > whether you're doing something wrong.
> > 
> >                                                          Pekka
> 
> Below is my baby module which only uses kmalloc and kfree for my device 
> structure. I found the slab corruption address is the address of the structure. 
> It seems to be a bug for kmalloc and kfree.

> /* The parameter for testing */
> int major=0;
> MODULE_PARM(major, "i");
> MODULE_PARM_DESC(major, "device major number");

Hi,
I had no problem loading and unloading your module on
2.6.17-rc1 [after changing MODULE_PARM() to
module_param(major, int, 0644);
].

---
~Randy
-
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/