From: Dave Hansen <haveblue@us.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andy Whitcroft <andyw@uk.ibm.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.15-rc4 panic in __nr_to_section() with CONFIG_SPARSEMEM
Date: Wed, 07 Dec 2005 15:34:15 -0800 [thread overview]
Message-ID: <1133998455.30387.67.camel@localhost> (raw)
In-Reply-To: <1133997772.21841.62.camel@localhost.localdomain>
On Wed, 2005-12-07 at 15:22 -0800, Badari Pulavarty wrote:
> On Wed, 2005-12-07 at 23:05 +0000, Andy Whitcroft wrote:
> > Badari Pulavarty wrote:
> > > Hi Andy,
> > >
> > > I getting a panic while doing "cat /proc/<pid>/smaps" on
> > > a process. I debugged a little to find out that faulting
> > > IP is in _nr_to_section() - seems to be getting somehow
> > > called by pte_offset_map_lock() from smaps_pte_range
> > > (which show_smaps) calls.
> > >
> > > Any ideas on why or how to debug further ?
> >
> > From dave's call graph I'd ask the question whether we should be calling
> > pfn_valid() before pfn_to_page(). When I reviewed the proposed
> > pfn_to_page() implementation I only recall one use and that already had
> > the pfn_valid() in it. I'll review -rc4 in the morning.
>
> BTW, the problem seems to be while dealing with shared memory areas
> that are backed by largepages.
Should you even be making it into the pte function with large pages?
Don't they just stop at the pmd level?
Maybe smaps_pmd_range() needs a pmd_huge() check.
-- Dave
next prev parent reply other threads:[~2005-12-07 23:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 22:37 2.6.15-rc4 panic in __nr_to_section() with CONFIG_SPARSEMEM Badari Pulavarty
2005-12-07 22:52 ` Dave Hansen
2005-12-07 23:05 ` Andy Whitcroft
2005-12-07 23:22 ` Badari Pulavarty
2005-12-07 23:34 ` Dave Hansen [this message]
2005-12-08 0:48 ` Dave Hansen
2005-12-08 16:07 ` Badari Pulavarty
2005-12-08 19:15 ` Dave Hansen
2005-12-08 19:33 ` Hugh Dickins
2005-12-08 19:47 ` Dave Hansen
2005-12-08 19:53 ` Badari Pulavarty
2005-12-08 23:48 ` David Gibson
2005-12-09 0:16 ` Dave Hansen
2005-12-12 16:19 ` Badari Pulavarty
2005-12-12 21:28 ` Dave Hansen
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=1133998455.30387.67.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=andyw@uk.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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