Greg Ungerer dc068f4621 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/2a462b23-5b8e-bbf4-ec7d-778434a3b9d7@google.com/T/#t Reported-by: Hugh Dickens <hughd@google.com> Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>		2022-05-16 13:18:30 +10:00
..
asm	m68knommu: set ZERO_PAGE() to the allocated zeroed page	2022-05-16 13:18:30 +10:00
uapi/asm	signal.h: add linux/signal.h and asm/signal.h to UAPI compile-test coverage	2022-02-17 09:09:36 +01:00