From: Andrew Morton <akpm@linux-foundation.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 11
Date: Tue, 15 Jun 2010 02:34:23 -0700 [thread overview]
Message-ID: <20100615023423.470bc963.akpm@linux-foundation.org> (raw)
In-Reply-To: <201006151856.38882.rusty@rustcorp.com.au>
On Tue, 15 Jun 2010 18:56:37 +0930 Rusty Russell <rusty@rustcorp.com.au> wrote:
> On Sat, 12 Jun 2010 09:01:24 am Andrew Morton wrote:
> > On Fri, 11 Jun 2010 14:17:38 +1000
> > Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > > I have created today's linux-next tree at
> > > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> > > (patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ).
> >
> > Rusty broke your kernel!
> >
> > oops: http://userweb.kernel.org/~akpm/IMG_20100611_155611.jpg
> >
> > config: http://userweb.kernel.org/~akpm/stuff/config-akpm2-small.txt
> >
> > (gdb) l *0xffffffff8105f9fb
> > 0xffffffff8105f9fb is in get_ksymbol (kernel/module.c:2784).
> > 2779 if (mod->symtab[i].st_shndx == SHN_UNDEF)
> > 2780 continue;
> > 2781
> > 2782 /* We ignore unnamed symbols: they're uninformative
> > 2783 * and inserted at a whim. */
> > 2784 if (mod->symtab[i].st_value <= addr
> > 2785 && mod->symtab[i].st_value > mod->symtab[best].st_value
> > 2786 && *(mod->strtab + mod->symtab[i].st_name) != '\0'
> > 2787 && !is_arm_mapping_symbol(mod->strtab + mod->symtab[i].st_name))
> > 2788 best = i;
>
> Hmm, I can't reproduce this :(
I haven't seen any reports from any other linux-next users either, so
I'm special.
> I'm only 32 bit here, have to dig out my
> 64-bit machine tomorrow.
>
> One wonders why we're in get_ksymbol at all. Has something already gone
> horribly wrong?
Nothing that I'm aware of. I guess I won't be getting a very good
trace if the trace uses get_ksymbol().
If it's still happening I'll debug it a bit. Need to find out why
netconsole went awol.
next prev parent reply other threads:[~2010-06-15 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 4:17 linux-next: Tree for June 11 Stephen Rothwell
2010-06-11 23:31 ` Andrew Morton
2010-06-15 9:26 ` Rusty Russell
2010-06-15 9:34 ` Andrew Morton [this message]
2010-06-23 22:53 ` Andrew Morton
2010-06-25 12:57 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2009-06-11 9:14 Stephen Rothwell
2008-06-11 9:38 Stephen Rothwell
2008-06-11 18:55 ` Greg KH
2008-06-12 0:17 ` Kevin Winchester
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=20100615023423.470bc963.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).