x86: mm: refer to the intended config STRICT_DEVMEM in a comment
authorLukas Bulwahn <lukas.bulwahn@gmail.com>
Thu, 7 Jul 2022 11:54:42 +0000 (13:54 +0200)
committerKees Cook <keescook@chromium.org>
Fri, 8 Jul 2022 17:49:03 +0000 (10:49 -0700)
commitc09327d5673e5fb3695e41d2c2f05b907abb8996
tree9224961900827f420dad022d5ae879cedf54d2ed
parent231af4709018a8e4f20e511da4b6506346d662d3
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.

Link: https://lore.kernel.org/r/f9074e8d-9314-9d7d-7bf5-5b5538c8be8d@intel.com/
Suggested-by: Dave Hansen <dave.hansen@intel.com>
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Link: https://lore.kernel.org/r/20220707115442.21107-1-lukas.bulwahn@gmail.com
arch/x86/mm/init.c