summaryrefslogtreecommitdiffstats
path: root/include/linux/uprobes.h
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@redhat.com>2012-09-14 18:52:10 +0200
committerAnton Arapov <anton@redhat.com>2012-10-29 11:50:12 +0100
commita9fcee1046ab98cb79f481f47850928789e55592 (patch)
treee067f0692dee4e546232db074c432144ea439eff /include/linux/uprobes.h
parent073fe1c2dff67340247a601ec3a1f302b0dbcd42 (diff)
downloadkernel-uprobes-a9fcee1046ab98cb79f481f47850928789e55592.tar.gz
kernel-uprobes-a9fcee1046ab98cb79f481f47850928789e55592.tar.xz
kernel-uprobes-a9fcee1046ab98cb79f481f47850928789e55592.zip
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>
Diffstat (limited to 'include/linux/uprobes.h')
-rw-r--r--include/linux/uprobes.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
index e6f0331e3d4..18d839da651 100644
--- a/include/linux/uprobes.h
+++ b/include/linux/uprobes.h
@@ -59,7 +59,6 @@ struct uprobe_consumer {
#ifdef CONFIG_UPROBES
enum uprobe_task_state {
UTASK_RUNNING,
- UTASK_BP_HIT,
UTASK_SSTEP,
UTASK_SSTEP_ACK,
UTASK_SSTEP_TRAPPED,