From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Dave Airlie <airlied@redhat.com>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Error: freeing invalid memtype
Date: Mon, 23 Mar 2009 12:07:20 -0700 [thread overview]
Message-ID: <20090323190720.GA16831@linux-os.sc.intel.com> (raw)
In-Reply-To: <49C572CC.6090704@gmail.com>
On Sat, Mar 21, 2009 at 04:05:48PM -0700, Kevin Winchester wrote:
> Pallipadi, Venkatesh wrote:
> > Kevin,
> >
> > Can you please send me the output of
> > # cat /debug/x86/pat_memtype_list
> >
> > (with debugfs mounted at /debug) as soon as you login into X and also
> > when you start seeing these errors with etracer and glxinfo.
> >
>
> Here is the output before attempting to run glxinfo:
> : :
> : :
>
> Does that help track down the problem? I am about to try disabling PAT
> in my config to see if that fixes things.
>
Can you please try the patch below and let me whether it helps.
Thanks,
Venki
x86, PAT: Change vma prot in pci_mmap to reflect inherited prot
While looking at the issue in the thread
http://marc.info/?l=dri-devel&m=123606627824556&w=2
noticed a bug in pci PAT code and memory type setting.
pci mmap code did not set the proper protection in vma, when it
inherited protection in reserve_memtype. This bug only affects
the case where there exists a WC mapping before X does an mmap
with /proc or /sys pci interface. This will cause X userlevel
mmap from /proc or /sysfs to fail on fork.
Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
diff --git a/arch/x86/pci/i386.c b/arch/x86/pci/i386.c
index 5ead808..f234a37 100644
--- a/arch/x86/pci/i386.c
+++ b/arch/x86/pci/i386.c
@@ -319,6 +319,9 @@ int pci_mmap_page_range(struct pci_dev *dev, struct vm_area_struct *vma,
return -EINVAL;
}
flags = new_flags;
+ vma->vm_page_prot = __pgprot(
+ (pgprot_val(vma->vm_page_prot) & ~_PAGE_CACHE_MASK) |
+ flags);
}
if (((vma->vm_pgoff < max_low_pfn_mapped) ||
next prev parent reply other threads:[~2009-03-23 19:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 23:28 Kevin Winchester
2009-03-18 18:12 ` Pallipadi, Venkatesh
2009-03-21 23:05 ` Kevin Winchester
2009-03-23 19:07 ` Pallipadi, Venkatesh [this message]
2009-03-23 19:48 ` Ingo Molnar
2009-03-23 21:27 ` Pallipadi, Venkatesh
2009-03-24 9:42 ` [tip:x86/pat] x86, PAT, PCI: Change vma prot in pci_mmap to reflect inherited prot Pallipadi, Venkatesh
2009-03-24 9:45 ` Pallipadi, Venkatesh
2009-03-24 22:19 ` Error: freeing invalid memtype Kevin Winchester
2009-03-24 22:25 ` Ingo Molnar
2009-04-09 3:00 ` Ryan Hill
2009-04-13 18:27 ` Jason D. Clinton
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=20090323190720.GA16831@linux-os.sc.intel.com \
--to=venkatesh.pallipadi@intel.com \
--cc=airlied@redhat.com \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome