From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, bpf@vger.kernel.org
Cc: daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, oleg@redhat.com, peterz@infradead.org,
mhiramat@kernel.org, jolsa@kernel.org, akpm@linux-foundation.org,
liam@infradead.org, ljs@kernel.org, surenb@google.com,
vbabka@kernel.org, jannh@google.com, hughd@google.com,
kees@kernel.org, mingo@redhat.com, tglx@kernel.org,
x86@kernel.org, linux-trace-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next 6/9] uprobes: Don't sleep on mmap_lock with dup_mmap_sem held in dup_mmap()
Date: Fri, 23 Oct 2026 22:51:06 +0200 [thread overview]
Message-ID: <6f1bd275-6751-4931-b996-b1c8ee6e4629@kernel.org> (raw)
In-Reply-To: <20261022015712.1297331-7-alexei.starovoitov@gmail.com>
On 10/22/26 03:57, Alexei Starovoitov wrote:
> From: Alexei Starovoitov <ast@kernel.org>
>
> dup_mm() takes dup_mmap_sem for reading and then dup_mmap() sleeps on
> mmap_lock of the parent. When another thread keeps that mmap_lock busy
> register_for_each_vma() waits for the reader, and every other fork() in
> the system waits for the writer. The parent doesn't have to map the file:
>
> A thread 1: mmap(MAP_POPULATE) -> mmap_read_lock(A)
> A thread 2: fork() -> percpu_down_read(&dup_mmap_sem),
> mmap_write_lock_killable(A) sleeps
> tracer: percpu_down_write(&dup_mmap_sem) sleeps
> others: fork() -> percpu_down_read(&dup_mmap_sem) sleeps
>
> dup_mmap() needs both locks. Don't sleep on one of them while holding
> the other. Sleep on mmap_lock and trylock dup_mmap_sem. If that fails sleep
> on dup_mmap_sem and trylock mmap_lock, and so on. Taking mmap_lock and then
> sleeping on dup_mmap_sem is simpler, but then all threads of the parent
> wait for mmap_lock as long as the writer holds dup_mmap_sem.
>
> Both are taken in dup_mmap() now, so release dup_mmap_sem there too.
> Commit 8ac662f5da19 ("fork: avoid inappropriate uprobe access to invalid
> mm") moved that to dup_mm() to hide the child from uprobes until mmput()
> when dup_mmap() fails. Since commit 43873af772f8 ("mm: change dup_mmap()
> recovery") dup_mmap() removes all vmas of such child before it drops
> mmap_lock.
>
> dup_mmap_sem is released before dup_userfaultfd_complete(), so the monitor
> that doesn't read UFFD_EVENT_FORK no longer blocks every fork(). During
> that wait register_for_each_vma() can find the child, while no task points
> to its mm. The next patch deals with that.
>
> Thread 1 of process A loops over mmap(4G, MAP_POPULATE) and munmap().
> Thread 2 calls fork() in a loop. Nobody maps the file. Process B calls
> fork() in a loop. 32 cpu VM. Median (max) of 15-25 runs, msec:
>
> the longest fork() in B attach
> before after before after
> uprobe_multi, 1 uprobe 206 (219) 0.10 (0.30) 220 11.7
> uprobe_multi, 4 uprobes 208 (428) 0.08 (0.32) 219 13.5
> perf_event, 4 uprobes 419 (424) 0.10 (0.44) 632 11.4
>
> During detach: 265-293 -> 0.19-0.37.
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> ---
> include/linux/uprobes.h | 5 +++++
> kernel/events/uprobes.c | 5 +++++
> kernel/fork.c | 4 ----
> mm/mmap.c | 19 +++++++++++++++++--
> 4 files changed, 27 insertions(+), 6 deletions(-)
>
> diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
> index d34dbc0fbbfe..6d74efa80d04 100644
> --- a/include/linux/uprobes.h
> +++ b/include/linux/uprobes.h
> @@ -211,6 +211,7 @@ extern void uprobe_unregister_sync(void);
> extern int uprobe_mmap(struct vm_area_struct *vma);
> extern void uprobe_munmap(struct vm_area_struct *vma, unsigned long start, unsigned long end);
> extern void uprobe_start_dup_mmap(void);
> +extern bool uprobe_try_start_dup_mmap(void);
> extern void uprobe_end_dup_mmap(void);
> extern void uprobe_dup_mmap(struct mm_struct *oldmm, struct mm_struct *newmm);
> extern void uprobe_free_utask(struct task_struct *t);
> @@ -277,6 +278,10 @@ uprobe_munmap(struct vm_area_struct *vma, unsigned long start, unsigned long end
> static inline void uprobe_start_dup_mmap(void)
> {
> }
> +static inline bool uprobe_try_start_dup_mmap(void)
> +{
> + return true;
> +}
> static inline void uprobe_end_dup_mmap(void)
> {
> }
> diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
> index a9274016c55d..92ccb730278f 100644
> --- a/kernel/events/uprobes.c
> +++ b/kernel/events/uprobes.c
> @@ -1927,6 +1927,11 @@ void uprobe_start_dup_mmap(void)
> percpu_down_read(&dup_mmap_sem);
> }
>
> +bool uprobe_try_start_dup_mmap(void)
> +{
> + return percpu_down_read_trylock(&dup_mmap_sem);
> +}
> +
> void uprobe_end_dup_mmap(void)
> {
> percpu_up_read(&dup_mmap_sem);
> diff --git a/kernel/fork.c b/kernel/fork.c
> index 10f2d05d816a..8fd6be932afe 100644
> --- a/kernel/fork.c
> +++ b/kernel/fork.c
> @@ -1539,11 +1539,9 @@ static struct mm_struct *dup_mm(struct task_struct *tsk,
> if (!mm_init(mm, tsk))
> goto fail_nomem;
>
> - uprobe_start_dup_mmap();
> err = dup_mmap(mm, oldmm);
> if (err)
> goto free_pt;
> - uprobe_end_dup_mmap();
>
> mm->hiwater_rss = get_mm_rss(mm);
> mm->hiwater_vm = mm->total_vm;
> @@ -1558,8 +1556,6 @@ static struct mm_struct *dup_mm(struct task_struct *tsk,
> mm->binfmt = NULL;
> mm_init_owner(mm, NULL);
> mmput(mm);
> - if (err)
> - uprobe_end_dup_mmap();
>
> fail_nomem:
> return NULL;
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 4bf26b0f1e6e..6ce654e33e3b 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -1713,8 +1713,22 @@ __latent_entropy int dup_mmap(struct mm_struct *mm, struct mm_struct *oldmm)
> LIST_HEAD(uf);
> VMA_ITERATOR(vmi, mm, 0);
>
> - if (mmap_write_lock_killable(oldmm))
> - return -EINTR;
> + /*
> + * Take mmap_lock of oldmm and dup_mmap_sem of uprobes.
> + * Don't sleep on one of them while holding the other.
> + */
> + for (;;) {
> + if (mmap_write_lock_killable(oldmm))
> + return -EINTR;
> + if (uprobe_try_start_dup_mmap())
> + break;
> + mmap_write_unlock(oldmm);
> +
> + uprobe_start_dup_mmap();
> + if (mmap_write_trylock(oldmm))
> + break;
> + uprobe_end_dup_mmap();
> + }
A note that I will have revised fix from Josef conflict with the changes here.
Nothing that cannot be worked around, but the whole "take writelock in dup_mmap"
is shaky as it seems.
--
Cheers,
David
next prev parent reply other threads:[~2026-10-23 20:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 1:57 [PATCH bpf-next 0/9] uprobes: Don't stall fork() when mmap_lock is busy Alexei Starovoitov
2026-10-22 1:57 ` [PATCH bpf-next 1/9] mm: Bring back mmap_write_trylock() Alexei Starovoitov
2026-10-22 2:02 ` sashiko-bot
2026-10-22 1:57 ` [PATCH bpf-next 2/9] uprobes: Don't run exit_mmap() under dup_mmap_sem Alexei Starovoitov
2026-10-22 2:04 ` sashiko-bot
2026-10-22 1:57 ` [PATCH bpf-next 3/9] uprobes/x86: Finish an unoptimization which failed half-way Alexei Starovoitov
2026-10-22 2:06 ` sashiko-bot
2026-10-22 2:57 ` Gregory Price (Meta)
2026-10-23 7:13 ` Jiri Olsa
2026-10-22 1:57 ` [PATCH bpf-next 4/9] uprobes/x86: Don't WARN if an optimized probe can't be written Alexei Starovoitov
2026-10-22 2:03 ` sashiko-bot
2026-10-22 2:37 ` bot+bpf-ci
2026-10-22 17:56 ` Jann Horn
2026-10-22 19:33 ` Liam R. Howlett
2026-10-23 14:06 ` Lorenzo Stoakes (ARM)
2026-10-23 7:13 ` Jiri Olsa
2026-10-22 1:57 ` [PATCH bpf-next 5/9] uprobes: Don't sleep on mmap_lock under dup_mmap_sem Alexei Starovoitov
2026-10-22 2:16 ` sashiko-bot
2026-10-22 2:37 ` bot+bpf-ci
2026-10-22 23:11 ` Andrii Nakryiko
2026-10-22 1:57 ` [PATCH bpf-next 6/9] uprobes: Don't sleep on mmap_lock with dup_mmap_sem held in dup_mmap() Alexei Starovoitov
2026-10-22 2:15 ` sashiko-bot
2026-10-22 18:42 ` Jann Horn
2026-10-23 20:51 ` David Hildenbrand (Arm) [this message]
2026-10-22 1:57 ` [PATCH bpf-next 7/9] fork: Let the new task point to its mm before uprobes can find it Alexei Starovoitov
2026-10-22 2:23 ` sashiko-bot
2026-10-22 1:57 ` [PATCH bpf-next 8/9] uprobes: Don't leak the breakpoints if the unregistering task is killed Alexei Starovoitov
2026-10-22 2:20 ` sashiko-bot
2026-10-22 1:57 ` [PATCH bpf-next 9/9] selftests/bpf: Test uprobes and fork() with busy mmap_lock Alexei Starovoitov
2026-10-22 2:10 ` sashiko-bot
2026-10-22 2:22 ` Alexei Starovoitov
2026-10-22 2:37 ` bot+bpf-ci
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=6f1bd275-6751-4931-b996-b1c8ee6e4629@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=memxor@gmail.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=vbabka@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox