public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [BUG] Page table corruption from commit 9542ada803198e6eba29d3289abb39ea82047b92.
Date: Thu, 22 Jan 2009 13:59:47 -0800	[thread overview]
Message-ID: <20090122215947.GH28352@linux-os.sc.intel.com> (raw)
In-Reply-To: <4978E3D6.1090903@suse.com>

On Thu, Jan 22, 2009 at 01:23:34PM -0800, Jeff Mahoney wrote:
> Ingo Molnar wrote:
> > Could you try the current -tip tree please?
> > 
> >   http://people.redhat.com/mingo/tip.git/README
> > 
> > There's a number of fixes in there that i think will fix your crash. In 
> > particular:
> > 
> >   9597134: x86: fix PTE corruption issue while mapping RAM using /dev/mem
> 
> Yep. That change fixed the corruption, but I still get the other
> warning. It originates with mainline commit
> 5899329b19100c0b82dc78e9b21ed8b920c9ffb3.

> WARNING: at arch/x86/mm/pat.c:637 reserve_pfn_range+0x5b/0x26d()

We are aware of this warning issue. We will soon have a fix for this.
For now, this is benign (essentially mmap of /dev/mem is doing
the reserve_memtype() twice, one through phys_mem_access_prot_allowed()
and reserve_pfn_range(). We are planning to remove this double
reserve, which should fix the warning).


> I get another warning at
> the bisect site, but it seems secondary. It doesn't occur in tip, though.
> 
> WARNING: at arch/x86/mm/pageattr.c:560 __change_page_attr_set_clr+0x10b/0xc0c() 
> CPA: called for zero pte. vaddr = ffff8800f7ff0000 cpa->vaddr = ffff8800f7ff0000

This one is fixed in tip by commit a1e46212a410793d575718818e81ddc442a65283
	x86: fix page attribute corruption with cpa()

thanks,
suresh

      reply	other threads:[~2009-01-22 21:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22  6:07 [BUG] Page table corruption from commit 9542ada803198e6eba29d3289abb39ea82047b92 Jeff Mahoney
2009-01-22  8:31 ` Ingo Molnar
2009-01-22 21:23   ` Jeff Mahoney
2009-01-22 21:59     ` Suresh Siddha [this message]

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=20090122215947.GH28352@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=hpa@zytor.com \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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