mtd: kernel BUG at arch/x86/mm/pat.c:279!
Suresh Siddha
suresh.b.siddha at intel.com
Fri Sep 7 18:42:58 EDT 2012
On Fri, 2012-09-07 at 11:14 -0700, Linus Torvalds wrote:
> Guys, this looks like a MTD and/or io_remap_pfn_range() bug, and it's
> not getting any traction.
>
> What the f*ck is mtd_mmap() doing, and why? The problem seems to be an
> overflow condition, because reserve_pfn_range() does
>
> reserve_memtype(paddr, paddr + size, want_flags, &flags);
>
> and then the BUG_ON() in reserve_memtype is
>
> BUG_ON(start >= end);
>
> so it very much looks like a paddr+size overflow. However, that makes
> little sense too, since we're working in "u64", so I suspect the
> overflow has happened somewhere earlier.
>
> I really don't see where, though. Could somebody please take a look?
> The mtdchar_mmap() types seem insane (why "u32" for len, for example?
> And that whole
>
> off = vma->vm_pgoff << PAGE_SHIFT;
>
> thing looks like it would overflow, since the whole point of pgoff is
> that if you shift it up by PAGE_SHIFT you need to also extend to
> 64-bit etc.
>
> So I would *guess* that it's the mtdchar_mmap() stuff that overflows
> due to bad types, but maybe it does deeper than that?
>
I started to look into this to see if this is a PAT issue but it does
indeed appear to be a mtd mmap issue.
Sasha, Does the appended fix the issue for you?
--8<--
From: Suresh Siddha <suresh.b.siddha at intel.com>
Subject: mtd: check the starting offset to be mmap'd
We need to check if both the starting offset aswell the total length
being mmap'd are with in the limits. With a large starting offset,
offset + (length-to-be-mapped) can wrap and appear smaller than the
limit. Need to check both start and end.
Also fix the types of the variables start, off, len.
Signed-off-by: Suresh Siddha <suresh.b.siddha at intel.com>
---
drivers/mtd/mtdchar.c | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/mtd/mtdchar.c b/drivers/mtd/mtdchar.c
index f2f482b..f79c0fa 100644
--- a/drivers/mtd/mtdchar.c
+++ b/drivers/mtd/mtdchar.c
@@ -1132,16 +1132,15 @@ static int mtdchar_mmap(struct file *file, struct vm_area_struct *vma)
struct mtd_file_info *mfi = file->private_data;
struct mtd_info *mtd = mfi->mtd;
struct map_info *map = mtd->priv;
- unsigned long start;
- unsigned long off;
- u32 len;
+ resource_size_t start, off;
+ unsigned long len;
if (mtd->type == MTD_RAM || mtd->type == MTD_ROM) {
off = vma->vm_pgoff << PAGE_SHIFT;
start = map->phys;
len = PAGE_ALIGN((start & ~PAGE_MASK) + map->size);
start &= PAGE_MASK;
- if ((vma->vm_end - vma->vm_start + off) > len)
+ if (off >= len || (vma->vm_end - vma->vm_start + off) > len)
return -EINVAL;
off += start;
More information about the linux-mtd
mailing list