summaryrefslogtreecommitdiff
path: root/scripts/objdiff
diff options
context:
space:
mode:
authorVasily Gorbik <gor@linux.ibm.com>2024-11-22 13:41:33 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-02-08 09:58:04 +0100
commit43f9177be438a28884aa04bb35824948151e6cfe (patch)
tree48d1c968dc21577fe28d78227491133b7860208e /scripts/objdiff
parent29c1fd9fddd2f3172594d8dc31507babb9021dc2 (diff)
downloadlinux-43f9177be438a28884aa04bb35824948151e6cfe.tar.gz
linux-43f9177be438a28884aa04bb35824948151e6cfe.tar.bz2
linux-43f9177be438a28884aa04bb35824948151e6cfe.zip
s390/mm: Allow large pages for KASAN shadow mapping
[ Upstream commit ff123eb7741638d55abf82fac090bb3a543c1e74 ] Commit c98d2ecae08f ("s390/mm: Uncouple physical vs virtual address spaces") introduced a large_allowed() helper that restricts which mapping modes can use large pages. This change unintentionally prevented KASAN shadow mappings from using large pages, despite there being no reason to avoid them. In fact, large pages are preferred for performance. Add POPULATE_KASAN_MAP_SHADOW to the allowed list in large_allowed() to restore large page mappings for KASAN shadows. While large_allowed() isn't strictly necessary with current mapping modes since disallowed modes either don't map anything or fail alignment and size checks, keep it for clarity. Fixes: c98d2ecae08f ("s390/mm: Uncouple physical vs virtual address spaces") Acked-by: Alexander Gordeev <agordeev@linux.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com> Signed-off-by: Heiko Carstens <hca@linux.ibm.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/objdiff')
0 files changed, 0 insertions, 0 deletions