From: Oleg Nesterov <oleg@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Anton Arapov <anton@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] uprobes: install_breakpoint() should fail if is_swbp_insn() == T
Date: Thu, 31 May 2012 20:53:39 +0200 [thread overview]
Message-ID: <20120531185339.GA28057@redhat.com> (raw)
In-Reply-To: <1338400450.28384.16.camel@twins>
On 05/30, Peter Zijlstra wrote:
>
> register's vma
> iteration is very careful not to have the same vma twice,
Hmm. I am wondering if it is careful enough...
Just in case, I think your patch is great. But it seems to me
there is another problem.
__find_next_vma_info() checks tmpvi->mm == vma->vm_mm to detect the
already visited mm/vma. However, afaics this can be false positive?
The caller, register_for_each_vma(), does mmput() and after that
this memory can be freed and re-used as another mm_struct.
I'll recheck this, but perhaps we need something like below?
Oleg.
--- x/kernel/events/uprobes.c
+++ x/kernel/events/uprobes.c
@@ -851,7 +851,6 @@ static int register_for_each_vma(struct
list_del(&vi->probe_list);
kfree(vi);
up_write(&mm->mmap_sem);
- mmput(mm);
continue;
}
vaddr = vma_address(vma, uprobe->offset);
@@ -860,7 +859,6 @@ static int register_for_each_vma(struct
list_del(&vi->probe_list);
kfree(vi);
up_write(&mm->mmap_sem);
- mmput(mm);
continue;
}
@@ -870,7 +868,6 @@ static int register_for_each_vma(struct
remove_breakpoint(uprobe, mm, vi->vaddr);
up_write(&mm->mmap_sem);
- mmput(mm);
if (is_register) {
if (ret && ret == -EEXIST)
ret = 0;
@@ -881,6 +878,7 @@ static int register_for_each_vma(struct
list_for_each_entry_safe(vi, tmpvi, &try_list, probe_list) {
list_del(&vi->probe_list);
+ mmput(vi->mm)
kfree(vi);
}
next prev parent reply other threads:[~2012-05-31 18:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 16:57 [PATCH 0/3] uprobes: misc minor changes Oleg Nesterov
2012-05-30 16:58 ` [PATCH 1/3] uprobes: install_breakpoint() should fail if is_swbp_insn() == T Oleg Nesterov
2012-05-30 17:28 ` Peter Zijlstra
2012-05-30 17:37 ` Srikar Dronamraju
2012-05-30 17:49 ` Peter Zijlstra
2012-05-30 17:54 ` Peter Zijlstra
2012-05-30 18:03 ` Peter Zijlstra
2012-05-30 18:04 ` Srikar Dronamraju
2012-05-30 18:21 ` Peter Zijlstra
2012-05-31 18:53 ` Oleg Nesterov [this message]
2012-06-01 15:53 ` Oleg Nesterov
2012-06-01 16:33 ` Srikar Dronamraju
2012-06-01 17:20 ` Oleg Nesterov
2012-06-01 18:31 ` Oleg Nesterov
2012-06-02 18:21 ` Oleg Nesterov
2012-06-01 16:47 ` Srikar Dronamraju
2012-06-01 18:38 ` Oleg Nesterov
2012-05-31 12:15 ` Peter Zijlstra
2012-05-31 12:54 ` Srikar Dronamraju
2012-05-30 16:58 ` [PATCH 2/3] uprobes: remove the unnecessary initialization in add_utask() Oleg Nesterov
2012-05-30 16:58 ` [PATCH 3/3] uprobes: simplify the usage of uprobe->pending_list Oleg Nesterov
2012-05-30 17:48 ` Srikar Dronamraju
2012-05-30 18:10 ` Oleg Nesterov
2012-05-30 18:23 ` Srikar Dronamraju
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=20120531185339.GA28057@redhat.com \
--to=oleg@redhat.com \
--cc=ananth@in.ibm.com \
--cc=anton@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).