From: Mike Rapoport <rppt@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: Check for YAMA ptrace_scope configuraiton before modifying it
Date: Tue, 10 Jun 2025 20:16:09 +0300 [thread overview]
Message-ID: <aEhoWVH0Ka6jB8QR@kernel.org> (raw)
In-Reply-To: <20250610-selftest-mm-enable-yama-v1-1-0097b6713116@kernel.org>
On Tue, Jun 10, 2025 at 03:07:44PM +0100, Mark Brown wrote:
> When running the memfd_secret test run_vmtests.sh unconditionally tries
> to confgiure the YAMA LSM's ptrace_scope configuration, leading to an error
> if YAMA is not in the running kernel:
>
> # ./run_vmtests.sh: line 432: /proc/sys/kernel/yama/ptrace_scope: No such file or directory
> # # ----------------------
> # # running ./memfd_secret
> # # ----------------------
>
> Check that this file is present before trying to write to it.
>
> The indentation here is a bit odd, and it doesn't seem great that we
> configure but don't restore ptrace_scope.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> tools/testing/selftests/mm/run_vmtests.sh | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/mm/run_vmtests.sh b/tools/testing/selftests/mm/run_vmtests.sh
> index dddd1dd8af14..33fc7fafa8f9 100755
> --- a/tools/testing/selftests/mm/run_vmtests.sh
> +++ b/tools/testing/selftests/mm/run_vmtests.sh
> @@ -429,7 +429,9 @@ CATEGORY="vma_merge" run_test ./merge
>
> if [ -x ./memfd_secret ]
> then
> -(echo 0 > /proc/sys/kernel/yama/ptrace_scope 2>&1) | tap_prefix
> +if [ -f /proc/sys/kernel/yama/ptrace_scope ]; then
> + (echo 0 > /proc/sys/kernel/yama/ptrace_scope 2>&1) | tap_prefix
> +fi
> CATEGORY="memfd_secret" run_test ./memfd_secret
> fi
>
>
> ---
> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
> change-id: 20250605-selftest-mm-enable-yama-1541c2d2ddcd
>
> Best regards,
> --
> Mark Brown <broonie@kernel.org>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-06-10 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 14:07 [PATCH] selftests/mm: Check for YAMA ptrace_scope configuraiton before modifying it Mark Brown
2025-06-10 17:16 ` Mike Rapoport [this message]
2025-06-11 13:20 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aEhoWVH0Ka6jB8QR@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.