summaryrefslogtreecommitdiffstats
path: root/tools/perf
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@linux-m68k.org>2017-09-05 22:57:06 +1000
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-12-09 22:01:48 +0100
commit510f6573ef5da5cc678e0fdb955f95c6125cd3bd (patch)
tree541c496cc9fe98c3a65f979569b53fdb71dfa518 /tools/perf
parente5f2421df13523e46697d453575c020af57c945b (diff)
downloadlinux-stable-510f6573ef5da5cc678e0fdb955f95c6125cd3bd.tar.gz
linux-stable-510f6573ef5da5cc678e0fdb955f95c6125cd3bd.tar.bz2
linux-stable-510f6573ef5da5cc678e0fdb955f95c6125cd3bd.zip
m68k: fix ColdFire node shift size calculation
[ Upstream commit f55ab8f27548ff3431a6567d400c6757c49fd520 ] The m68k pg_data_table is a fix size array defined in arch/m68k/mm/init.c. Index numbers within it are defined based on memory size. But for Coldfire these don't take into account a non-zero physical RAM base address, and this causes us to access past the end of this array at system start time. Change the node shift calculation so that we keep the index inside its range. Reported-by: Angelo Dureghello <angelo@sysam.it> Tested-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org> Signed-off-by: Sasha Levin <alexander.levin@verizon.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf')
0 files changed, 0 insertions, 0 deletions