summaryrefslogtreecommitdiff
path: root/Kbuild
diff options
context:
space:
mode:
authorPaul Mundt <lethal@linux-sh.org>2010-01-20 12:10:30 +0300
committerPaul Mundt <lethal@linux-sh.org>2010-01-20 12:10:30 +0300
commit920efaabcbd34e6b8dc05c5b777df3e936af5812 (patch)
tree34645e1ebe93a3a7365eb85b15d358e467e71f1b /Kbuild
parentb51989b8afe9409ee68c67ce2a5de4390693bd2b (diff)
downloadlinux-920efaabcbd34e6b8dc05c5b777df3e936af5812.tar.xz
sh: Correct iounmap fixmap teardown.
iounmap_fixed() had a couple of bugs in it that caused it to effectively fail at life. The total number of pages to unmap factored in the mapping offset and aligned up to the next page boundary, which doesn't match the ioremap_fixed() behaviour. When ioremap_fixed() pegs a slot, the address in the mapping data already contains the offset displacement, and the size is recorded verbatim given that we're only interested in total number of pages required. As such, we need to calculate the total number from the original size in the unmap path as well. At the same time, there was also an off-by-1 problem in the fixmap index calculation which has also been corrected. Previously subsequent remaps of an identical fixmap index would trigger the pte_ERROR() in set_pte_phys(): arch/sh/mm/init.c:77: bad pte 8053ffb0(0000781003fff506). arch/sh/mm/init.c:77: bad pte 8053ffb0(0000781003fff506). arch/sh/mm/init.c:77: bad pte 8053ffb0(0000781003fff506). arch/sh/mm/init.c:77: bad pte 8053ffb0(0000781003fff506). arch/sh/mm/init.c:77: bad pte 8053ffb0(0000781003fff506). arch/sh/mm/init.c:77: bad pte 8053ffb0(0000781003fff506). With this patch in place, the iounmap-driven fixmap teardown actually does what it's supposed to do. Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions