From: Oleg Nesterov <oleg@redhat.com>
Date: Fri, 14 Sep 2012 16:52:10 +0000 (+0200)
Subject: uprobes: Kill UTASK_BP_HIT state
X-Git-Tag: v3.7-rc3~40^2~1^2~15
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1b08e907211cdc744f54871736005d9f3e7f182c;p=pandora-kernel.git

uprobes: Kill UTASK_BP_HIT state

Kill UTASK_BP_HIT state, it buys nothing but complicates the code.
It is only used in uprobe_notify_resume() to decide who should be
called, we can check utask->active_uprobe != NULL instead. And this
allows us to simplify handle_swbp(), no need to clear utask->state.

Likewise we could kill UTASK_SSTEP, but UTASK_BP_HIT is worse and
imho should die. The problem is, it creates the special case when
task->utask is NULL, we can't distinguish RUNNING and BP_HIT. With
this patch utask == NULL always means RUNNING.

Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
---

Reading git-diff-tree failed