On Sun, 2011-03-06 at 16:04 -0500, Andy Walls wrote:
> On Sun, 2011-03-06 at 10:37 -0800, Hugh Dickins wrote:
> >
> > Thanks for all the effort you are putting into investigating this: you
> > deserve a better response than I can give you.
> >
> > mm/vmalloc.c's vmap_area handling is entirely separate from
> > mm/mmap.c's vm_area_struct handling, yet both misbehaviors would be
> > explained if a next pointer has been corrupted to NULL.
> >
> > Probably just coincidence that they both manifest that way, though the
> > underlying problem may turn out to be one.
> > If you have not already, it would be well worth turning on
> > CONFIG_DEBUG_LIST and CONFIG_DEBUG_SLAB or CONFIG_SLUB_DEBUG with
> > CONFIG_SLUB_DEBUG_ON.
>
> > But you are having trouble
> > reproducing it yourself?
>
> I can't say yet. I'm currently two for two.
After backing up the machine and testing again, I'm now 3 for 3.
This time it happened in the memset() in kernel/module.c:move_module()
when modprobe was trying to load the cx18-alsa.ko module.
static int move_module(struct module *mod, struct load_info
*info)
{
int i;
void *ptr;
/* Do the allocs. */
ptr = module_alloc_update_bounds(mod->core_size);
/*
* The pointer to this block is stored in the module structure
* which is inside the block. Just mark it as not being
a
* leak.
*/
kmemleak_not_leak(ptr);
if (!ptr)
return -ENOMEM;
memset(ptr, 0, mod->core_size); <----- Ooops/BUG
/home/andy/cx18dev/git/media_tree/kernel/module.c:2529
385c: 41 8b 8c 24 64 01 00 mov 0x164(%r12),%ecx
3863: 00
3864: 31 c0 xor %eax,%eax
3866: 48 89 d7 mov %rdx,%rdi
3869: f3 aa rep stos %al,%es:(%rdi) <----- Oops/BUG
ptr had a value of 0x0000000000001000
I'm starting a git bisect now.
Regards,
Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
