diff options
| author | Oleg Nesterov <oleg@redhat.com> | 2012-09-14 16:52:10 (GMT) |
|---|---|---|
| committer | Oleg Nesterov <oleg@redhat.com> | 2012-09-29 19:21:53 (GMT) |
| commit | 1b08e907211cdc744f54871736005d9f3e7f182c (patch) | |
| tree | df62046438501ecd89e0bac1fb9b73edaf622e15 /arch/x86/kernel/entry_32.S | |
| parent | 0578a97098dab967ece4b025fe5eb4984c4c86c0 (diff) | |
| download | linux-fsl-qoriq-1b08e907211cdc744f54871736005d9f3e7f182c.tar.xz | |
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 'arch/x86/kernel/entry_32.S')
0 files changed, 0 insertions, 0 deletions