From: Andrea Cervesato <andrea.cervesato@suse.de>
To: Linux Test Project <ltp@lists.linux.it>
Subject: [LTP] [PATCH v3 0/2] Fix cma testing suite permissions
Date: Tue, 20 Oct 2026 12:37:28 +0200 [thread overview]
Message-ID: <20261020-fix_process_vm_writev_permissions-v3-0-1e92d7a29aef@suse.com> (raw)
The cma testing suite started to fail on modern systems enabling YAMA.
Unfortunately, using CAP_PTRACE capability for users is not enough to
avoid an EPERM. For this reason, it's better to require root and fix the
whole suite in one shot.
Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
---
Changes in v3:
- add CAP_SYS_PTRACE fallback in lapi/capability.h
- Link to v2: https://lore.kernel.org/20261014-fix_process_vm_writev_permissions-v2-1-17710f74606c@suse.com
Changes in v2:
- consider mode 1, 2, 3 and user
- Link to v1: https://lore.kernel.org/20261014-fix_process_vm_writev_permissions-v1-1-6affee2da859@suse.com
---
Andrea Cervesato (2):
lapi/capability.h: Add CAP_SYS_PTRACE fallback
syscalls/cma: Handle Yama ptrace_scope in tests
include/lapi/capability.h | 4 +++
testcases/kernel/syscalls/cma/cma.h | 38 ++++++++++++++++++++++
testcases/kernel/syscalls/cma/process_vm_readv02.c | 5 +++
testcases/kernel/syscalls/cma/process_vm_readv03.c | 5 +++
.../kernel/syscalls/cma/process_vm_writev02.c | 5 +++
5 files changed, 57 insertions(+)
---
base-commit: 1aae0e4d9d1e2e7818fda773b372cee8fb856de7
change-id: 20261014-fix_process_vm_writev_permissions-6fca6598d9fb
Best regards,
--
Andrea Cervesato <andrea.cervesato@suse.com>
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2026-10-20 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 10:37 Andrea Cervesato [this message]
2026-10-20 10:37 ` [LTP] [PATCH v3 1/2] lapi/capability.h: Add CAP_SYS_PTRACE fallback Andrea Cervesato
2026-10-20 14:51 ` [LTP] " linuxtestproject.agent
2026-10-20 10:37 ` [LTP] [PATCH v3 2/2] syscalls/cma: Handle Yama ptrace_scope in tests Andrea Cervesato
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=20261020-fix_process_vm_writev_permissions-v3-0-1e92d7a29aef@suse.com \
--to=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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.