From: Lukas Bulwahn Date: Thu, 7 Jul 2022 11:54:42 +0000 (+0200) Subject: x86/mm: Refer to the intended config STRICT_DEVMEM in a comment X-Git-Tag: v6.1-rc5~802^2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=9de76f41ea2188f2784f48352f9278819d249afc;p=platform%2Fkernel%2Flinux-starfive.git x86/mm: Refer to the intended config STRICT_DEVMEM in a comment Commit a4866aa81251 ("mm: Tighten x86 /dev/mem with zeroing reads") adds a comment to the function devmem_is_allowed() referring to a non-existing config STRICT_IOMEM, whereas the comment very likely intended to refer to the config STRICT_DEVMEM, as the commit adds some behavior for the config STRICT_DEVMEM. Most of the initial analysis was actually done by Dave Hansen in the email thread below (see Link). Refer to the intended and existing config STRICT_DEVMEM. Suggested-by: Dave Hansen Signed-off-by: Lukas Bulwahn Signed-off-by: Dave Hansen Link: https://lore.kernel.org/r/f9074e8d-9314-9d7d-7bf5-5b5538c8be8d@intel.com/ Link: https://lkml.kernel.org/r/20220707115442.21107-1-lukas.bulwahn@gmail.com --- diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c index d8cfce2..5d747a1 100644 --- a/arch/x86/mm/init.c +++ b/arch/x86/mm/init.c @@ -846,7 +846,7 @@ int devmem_is_allowed(unsigned long pagenr) /* * This must follow RAM test, since System RAM is considered a - * restricted resource under CONFIG_STRICT_IOMEM. + * restricted resource under CONFIG_STRICT_DEVMEM. */ if (iomem_is_exclusive(pagenr << PAGE_SHIFT)) { /* Low 1MB bypasses iomem restrictions. */