summaryrefslogtreecommitdiff
path: root/drivers/nvmem/qfprom.c
diff options
context:
space:
mode:
authorVasily Gorbik <gor@linux.ibm.com>2024-11-22 15:41:33 +0300
committerHeiko Carstens <hca@linux.ibm.com>2024-11-24 18:59:51 +0300
commitff123eb7741638d55abf82fac090bb3a543c1e74 (patch)
treee8fba53ebe0db096d17020aad5f246e8ec038517 /drivers/nvmem/qfprom.c
parent9de3e4bf6cfbcb62e9ec658e3b291cd479018b43 (diff)
downloadlinux-ff123eb7741638d55abf82fac090bb3a543c1e74.tar.xz
s390/mm: Allow large pages for KASAN shadow mapping
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>
Diffstat (limited to 'drivers/nvmem/qfprom.c')
0 files changed, 0 insertions, 0 deletions