| commit | 17ebba1fe4da4b5d62782be8743e0e8231812af9 | |
| author | Nicolas Pitre <nico@fluxnic.net> | |
| Mon, 7 Jun 2010 20:28:55 +0000 (7 21:28 +0100) | ||
| committer | Russell King <rmk+kernel@arm.linux.org.uk> | |
| Tue, 8 Jun 2010 18:25:50 +0000 (8 19:25 +0100) | ||
| tree | aef818d66f5dbe04817b88b8d0351035740118ba | treesnapshot (tar.gz zip) |
| parent | b394eebdd3d436f1796e53b97799554c5aa77431 | commitdiff |
ARM: 6165/1: trap overflows on highmem pages from kmap_atomic when debugging
When CONFIG_DEBUG_HIGHMEM is used, the fixmap entry used for a highmem page
by kmap_atomic() is always cleared by kunmap_atomic(). This helps find
bad usages such as dereferences after the unmap, or overflow into the
adjacent fixmap areas.
But this debugging aid is completely bypassed when a kmap for the same
page already exists as the kmap is reused instead. ON VIVT systems we
have no choice but to reuse that kmap due to cache coherency issues,
but on non VIVT systems we should always force the fixmap usage when
debugging is active.
Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
When CONFIG_DEBUG_HIGHMEM is used, the fixmap entry used for a highmem page
by kmap_atomic() is always cleared by kunmap_atomic(). This helps find
bad usages such as dereferences after the unmap, or overflow into the
adjacent fixmap areas.
But this debugging aid is completely bypassed when a kmap for the same
page already exists as the kmap is reused instead. ON VIVT systems we
have no choice but to reuse that kmap due to cache coherency issues,
but on non VIVT systems we should always force the fixmap usage when
debugging is active.
Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
| arch/arm/mm/highmem.c | diffblobblamehistory |