From: Andy Walls <awalls@md.metrocast.net>
To: Hugh Dickins <hughd@google.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
David Miller <davem@davemloft.net>,
linux-media@vger.kernel.org,
Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: BUG at mm/mmap.c:2309 when cx18.ko and cx18-alsa.ko loaded
Date: Tue, 08 Mar 2011 19:37:01 -0500 [thread overview]
Message-ID: <1299631021.3023.10.camel@localhost> (raw)
In-Reply-To: <1299445446.2310.157.camel@localhost>
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
next prev parent reply other threads:[~2011-03-09 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 2:06 BUG at mm/mmap.c:2309 when cx18.ko and cx18-alsa.ko loaded Andy Walls
2011-03-04 15:50 ` Devin Heitmueller
2011-03-04 17:13 ` Andy Walls
2011-03-07 10:32 ` Takashi Iwai
2011-03-05 21:59 ` Andy Walls
2011-03-06 2:03 ` Andy Walls
2011-03-06 18:37 ` Hugh Dickins
2011-03-06 21:04 ` Andy Walls
2011-03-07 2:34 ` Hugh Dickins
2011-03-09 0:37 ` Andy Walls [this message]
2011-03-11 0:34 ` Andy Walls
2011-03-11 0:47 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1299631021.3023.10.camel@localhost \
--to=awalls@md.metrocast.net \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=dheitmueller@kernellabs.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox