Re: [PATCH 1/2] uprobes: document the usage of mm->mmap_lock
From: Oleg Nesterov
Date: Thu Jul 11 2024 - 11:27:55 EST
On 07/11, Masami Hiramatsu wrote:
>
> What about this?
>
> * We take mmap_lock for writing to avoid the race with
> * find_active_uprobe(), which takes mmap_lock for reading.
> * Thus this install_breakpoint() must not make
> * is_trap_at_addr() true right after find_uprobe()
> * returns NULL in find_active_uprobe().
Thanks! will change.
Oleg.