Re: [PATCH v2 02/12] uprobes: correct mmap_sem locking assumptions in uprobe_write_opcode()
From: Oleg Nesterov <oleg@redhat.com>
Date: 2024-07-03 11:42:51
Also in:
bpf
From: Oleg Nesterov <oleg@redhat.com>
Date: 2024-07-03 11:42:51
Also in:
bpf
On 07/01, Andrii Nakryiko wrote:
--- a/kernel/events/uprobes.c +++ b/kernel/events/uprobes.c@@ -453,7 +453,7 @@ static int update_ref_ctr(struct uprobe *uprobe, struct mm_struct *mm, * @vaddr: the virtual address to store the opcode. * @opcode: opcode to be written at @vaddr. * - * Called with mm->mmap_lock held for write. + * Called with mm->mmap_lock held for read or write. * Return 0 (success) or a negative errno.
Thanks, Acked-by: Oleg Nesterov <oleg@redhat.com> I'll try to send the patch which explains the reasons for mmap_write_lock() in register_for_each_vma() later. Oleg.