From: Cyril Hrubis <chrubis@suse.cz>
To: Jan Polensky <japo@linux.ibm.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v6 1/1] thp04: Add ptrace mode and fix tracee stop synchronization
Date: Fri, 10 Jul 2026 14:02:04 +0200 [thread overview]
Message-ID: <alDfPHAbN8nssBgX@rei> (raw)
In-Reply-To: <alDbqPsc3ueUqXlN@li-276bd24c-2dcc-11b2-a85c-945b6f05615c.ibm.com>
Hi!
> That's a fair point.
>
> The main goal was to keep thp04 functional on kernels with
> CONFIG_PROC_MEM_FORCE_PTRACE=y, where direct writes via /proc/self/mem
> are no longer possible.
>
> Do you have a preference for how support for that configuration should
> look?
>
> Would you prefer:
>
> 1. Keeping thp04 focused on the original race test and skipping it
> when only ptrace-based writes are available?
>
> 2. Splitting the ptrace write validation into a separate testcase and
> leaving thp04 unchanged?
>
> 3. Some other approach?
1 + 2 please.
The thp04 is a CVE regression test, if there is no chance to trigger the
CVE it should just report TCONF.
> I'm mostly trying to understand the intended coverage for
> CONFIG_PROC_MEM_FORCE_PTRACE=y before making further changes.
For that we should add tests under testcases/syscalls/ptrace/. I suppose
that we need a test that would check that the process cannot modify
itself when that config option is enabled. And another test that would
validate that parent can access child memory.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-07-10 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 17:59 [LTP] [PATCH v6 1/1] thp04: Add ptrace mode and fix tracee stop synchronization Jan Polensky
2026-07-09 18:56 ` [LTP] " linuxtestproject.agent
2026-07-10 11:26 ` [LTP] [PATCH v6 1/1] " Cyril Hrubis
2026-07-10 11:46 ` Jan Polensky
2026-07-10 12:02 ` Cyril Hrubis [this message]
2026-07-14 15:12 ` Jan Polensky
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=alDfPHAbN8nssBgX@rei \
--to=chrubis@suse.cz \
--cc=japo@linux.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox