diff options
| author | Nicolas Pitre <nicolas.pitre@linaro.org> | 2012-06-27 17:28:57 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-07-16 09:03:22 -0700 |
| commit | 937bff779cd840aca9f74dd7f2d43dafad3979bb (patch) | |
| tree | 0292851c004d3bd9f47b138698dc47695eedd950 /ipc | |
| parent | 45500e587ad1c2ea809c52961675c4eb9befcab5 (diff) | |
| download | linux-3.10-937bff779cd840aca9f74dd7f2d43dafad3979bb.tar.gz linux-3.10-937bff779cd840aca9f74dd7f2d43dafad3979bb.tar.bz2 linux-3.10-937bff779cd840aca9f74dd7f2d43dafad3979bb.zip | |
ARM: 7438/1: fill possible PMD empty section gaps
commit 19b52abe3c5d759661500a1dc810924369b2ad46 upstream.
On ARM with the 2-level page table format, a PMD entry is represented by
two consecutive section entries covering 2MB of virtual space.
However, static mappings always were allowed to use separate 1MB section
entries. This means in practice that a static mapping may create half
populated PMDs via create_mapping().
Since commit 0536bdf33f (ARM: move iotable mappings within the vmalloc
region) those static mappings are located in the vmalloc area. We must
ensure no such half populated PMDs are accessible once vmalloc() or
ioremap() start looking at the vmalloc area for nearby free virtual
address ranges, or various things leading to a kernel crash will happen.
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Reported-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: "R, Sricharan" <r.sricharan@ti.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions