On 4/16/26 20:40, Mark Brown wrote:
> 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 commit 599bbba5a36f ("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.
>
> Reported-by: Aishwarya TCV <[email protected]>
> Signed-off-by: Mark Brown <[email protected]>
> ---
I guess we could teach most tests to SKIP if /proc/pid/mem is unusable.
Acked-by: David Hildenbrand (Arm) <[email protected]>
--
Cheers,
David
