From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Alban Crequy <alban.crequy@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Alban Crequy <albancrequy@microsoft.com>,
Peter Xu <peterx@redhat.com>, Willy Tarreau <w@1wt.eu>,
linux-kselftest@vger.kernel.org, shuah@kernel.org,
Usama Arif <usama.arif@linux.dev>,
David Laight <david.laight.linux@gmail.com>
Subject: Re: [PATCH v5 1/2] mm/process_vm_access: pidfd and nowait support for process_vm_readv/writev
Date: Wed, 3 Jun 2026 15:54:57 +0200 [thread overview]
Message-ID: <8e738cc8-dce8-4043-9b93-2bb867c43028@kernel.org> (raw)
In-Reply-To: <20260603082707.3831525-1-alban.crequy@gmail.com>
> However, the exited-leader case is a real limitation for profilers.
> OpenTelemetry eBPF Profiler wants to profile a process where the main thread
> has exited but secondary threads are still running [2].
> [2] https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/376
>
> Using plain TIDs (flags=0) would work, but it means users cannot use
> PROCESS_VM_PIDFD in this scenario.
>
> What do you think this patch should do? I see two options:
> - Address this limitation in a separate future patch that fixes
> pidfd_get_task() to use PIDTYPE_PID when PIDFD_THREAD is detected in
> f_flags, benefiting all callers (process_vm_readv, process_madvise,
> and any future users).
Extending it consistently for that scenario seems like the right thing to do?
@Christian?
--
Cheers,
David
next prev parent reply other threads:[~2026-06-03 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 10:09 [PATCH v5 0/2] " Alban Crequy
2026-06-02 10:09 ` [PATCH v5 1/2] " Alban Crequy
2026-06-02 12:16 ` David Hildenbrand (Arm)
2026-06-03 8:27 ` Alban Crequy
2026-06-03 13:54 ` David Hildenbrand (Arm) [this message]
2026-06-04 12:49 ` Christian Brauner
2026-06-05 9:31 ` David Hildenbrand (Arm)
2026-06-04 12:59 ` Christian Brauner
2026-06-02 10:09 ` [PATCH v5 2/2] selftests/mm: add tests for process_vm_readv flags Alban Crequy
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=8e738cc8-dce8-4043-9b93-2bb867c43028@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alban.crequy@gmail.com \
--cc=albancrequy@microsoft.com \
--cc=brauner@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®