mirror of
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
synced 2026-11-06 09:33:20 +01:00
Mark Brown
a3907a3169
Several of the mm selftests made use of /proc/pid/mem as part of their operation but we do not specify this in the config fragment for them, at least mkdirty and ksm_functional_tests have this requirement. This has been working fine in practice since PROC_MEM_ALWAYS_FORCE was the default setting but commit599bbba5a3("proc: make PROC_MEM_FORCE_PTRACE the Kconfig default") that is no longer the case, meaning that tests run on kernels built based on defconfigs have started having the new more restrictive default and failing. Add PROC_MEM_ALWAYS_FORCE to the config fragment for the mm selftests. Thanks to Aishwarya TCV for spotting the issue and identifying the commit that introduced it. Link: https://lore.kernel.org/20260416-selftests-mm-proc-mem-always-force-v1-1-3f5865153c67@kernel.org Fixes:599bbba5a3("proc: make PROC_MEM_FORCE_PTRACE the Kconfig default") Signed-off-by: Mark Brown <[email protected]> Reported-by: Aishwarya TCV <[email protected]> Reviewed-by: Mike Rapoport (Microsoft) <[email protected]> Acked-by: David Hildenbrand (Arm) <[email protected]> Reviewed-by: Anshuman Khandual <[email protected]> Reviewed-by: Dev Jain <[email protected]> Cc: Lorenzo Stoakes <[email protected]> Cc: Michal Hocko <[email protected]> Cc: Mike Rapoport <[email protected]> Cc: Shuah Khan <[email protected]> Cc: Suren Baghdasaryan <[email protected]> Signed-off-by: Andrew Morton <[email protected]>
17 lines
357 B
Plaintext
17 lines
357 B
Plaintext
CONFIG_SYSVIPC=y
|
|
CONFIG_USERFAULTFD=y
|
|
CONFIG_PTE_MARKER_UFFD_WP=y
|
|
CONFIG_TEST_VMALLOC=m
|
|
CONFIG_DEVICE_PRIVATE=y
|
|
CONFIG_TEST_HMM=m
|
|
CONFIG_GUP_TEST=y
|
|
CONFIG_TRANSPARENT_HUGEPAGE=y
|
|
CONFIG_MEM_SOFT_DIRTY=y
|
|
CONFIG_ANON_VMA_NAME=y
|
|
CONFIG_FTRACE=y
|
|
CONFIG_PROFILING=y
|
|
CONFIG_UPROBES=y
|
|
CONFIG_MEMORY_FAILURE=y
|
|
CONFIG_HWPOISON_INJECT=m
|
|
CONFIG_PROC_MEM_ALWAYS_FORCE=y
|