Skip to content

uprobes: Change handle_swbp() to expose bp_vaddr to handler_chain()

Oleg Nesterov lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2uprobes/x86: Change __skip_sstep() to actually skip the whole insnarch/x86/kernel/uprobes.c+4 -13 replies
2/2uprobes: Change handle_swbp() to expose bp_vaddr to handler_chain()arch/x86/kernel/uprobes.c kernel/events/uprobes.c kernel/trace/trace_uprobe.c+9 -112 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchAnanth N MavinakayanahalliSrikar Dronamraju
1/2A-b A-b
2/2A-b A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] uprobes: Change handle_swbp() to expose bp_vaddr to handler_chain()

Hello.

Inspired by the recent uretrpobe RFC's. I think it simply makes no sense to call handler/skip/arch_uprobe_pre_xol with regs->ip pointing to the "random" address after the task hits bp.

Ananth, could you please confirm 2/2 can't break powerpc? It "obviously" shouldn't because uprobe_get_swbp_addr() is a "nop" on ppc, but still your ack is welcomed.

Oleg.