tree 95c76676a23f8d57731681f5987084f05555af15
parent 750deaa4021da1cf9fdb1e20861a10c76fd7f2bc
author Dave Hansen <haveblue@us.ibm.com> 1130713177 -0800
committer Linus Torvalds <torvalds@g5.osdl.org> 1130722632 -0800

[PATCH] fixup bogus e820 entry with mem=

This was reported because someone was getting oopses reading /proc/iomem.
It was tracked down to a zero-sized 'struct resource' entry which was
located right at 4GB.

You need two conditions to hit this bug: a BIOS E820_RAM area starting at
exactly the boundary where you specify mem= (to get a zero-sized entry),
and for the legacy_init_iomem_resources() loop to skip that resource (which
only happens at exactly 4G).

I think the killing zero-sized e820 entry is the easiest way to fix this.

Signed-off-by: Dave Hansen <haveblue@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>