aboutsummaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/mm.py
diff options
context:
space:
mode:
authorGreg Ungerer <[email protected]>2022-04-20 23:27:47 +1000
committerGreg Ungerer <[email protected]>2022-05-16 13:18:30 +1000
commitdc068f46217970d9516f16cd37972a01d50dc055 (patch)
tree90d1fce067e04440fd9eff6ea5ae83c18546524d /scripts/gdb/linux/mm.py
parent42226c989789d8da4af1de0c31070c96726d990c (diff)
m68knommu: set ZERO_PAGE() to the allocated zeroed page
The non-MMU m68k pagetable ZERO_PAGE() macro is being set to the somewhat non-sensical value of "virt_to_page(0)". The zeroth page is not in any way guaranteed to be a page full of "0". So the result is that ZERO_PAGE() will almost certainly contain random values. We already allocate a real "empty_zero_page" in the mm setup code shared between MMU m68k and non-MMU m68k. It is just not hooked up to the ZERO_PAGE() macro for the non-MMU m68k case. Fix ZERO_PAGE() to use the allocated "empty_zero_page" pointer. I am not aware of any specific issues caused by the old code. Link: https://lore.kernel.org/linux-m68k/[email protected]/T/#t Reported-by: Hugh Dickens <[email protected]> Signed-off-by: Greg Ungerer <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/mm.py')
0 files changed, 0 insertions, 0 deletions