From: Oleg Nesterov <oleg@redhat.com>
To: Anton Arapov <anton@redhat.com>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Josh Stone <jistone@redhat.com>, Frank Eigler <fche@redhat.com>
Subject: Re: [RFC PATCH 4/6] uretprobes: invoke return probe handlers
Date: Sat, 22 Dec 2012 17:29:24 +0100 [thread overview]
Message-ID: <20121222162924.GD18082@redhat.com> (raw)
In-Reply-To: <1356088596-17858-5-git-send-email-anton@redhat.com>
On 12/21, Anton Arapov wrote:
>
> +static unsigned long uretprobe_run_handlers(struct pt_regs *regs)
> +{
> + struct hlist_head *head;
> + struct hlist_node *r1, *r2;
> +
> + struct return_instance *ri;
> + struct uprobe_task *utask;
> +
> + struct xol_area *area;
> + unsigned long rp_trampoline_vaddr;
> + unsigned long orig_return_vaddr, cur_sp;
> +
> + cur_sp = (unsigned long)regs->sp;
This depends on arch/.
BTW, this series will break the compilation on powerpc, I guess.
> + hlist_for_each_entry_safe(ri, r1, r2, head, hlist) {
> + if (ri->uprobe
it should never be NULL, no?
> && ri->uprobe->return_consumers)
> + uretprobe_handler_chain(ri->uprobe, ri->orig_return_vaddr, regs);
^^^^^^^^^^^^^^^^^
->orig_return_vaddr can be rp_trampoline_vaddr. Not sure ->handler()
wants this value ;)
> @@ -1567,12 +1625,23 @@ static void handle_swbp(struct pt_regs *regs)
> {
> struct uprobe_task *utask;
> struct uprobe *uprobe;
> - unsigned long bp_vaddr;
> + struct xol_area *area;
> + unsigned long bp_vaddr, orig_return_vaddr;
> int uninitialized_var(is_swbp);
>
> bp_vaddr = uprobe_get_swbp_addr(regs);
> - uprobe = find_active_uprobe(bp_vaddr, &is_swbp);
> + area = get_xol_area(current->mm);
> + if (area) {
> + if (bp_vaddr == area->rp_trampoline_vaddr) {
> + orig_return_vaddr = uretprobe_run_handlers(regs);
> + instruction_pointer_set(regs, orig_return_vaddr);
> + if (current->utask->doomed)
> + send_sig(SIGSEGV, current, 0);
Just move this send_sig() into uretprobe_run_handlers() and kill
the ugly utask->doomed.
Oleg.
next prev parent reply other threads:[~2012-12-22 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 11:16 [RFC PATCH 0/6] uprobes: return probe implementation Anton Arapov
2012-12-21 11:16 ` [RFC PATCH 1/6] uretprobes/x86: hijack return address Anton Arapov
2012-12-22 16:02 ` Oleg Nesterov
2012-12-21 11:16 ` [RFC PATCH 2/6] uretprobes: trampoline implementation Anton Arapov
2012-12-22 16:02 ` Oleg Nesterov
2012-12-21 11:16 ` [RFC PATCH 3/6] uretprobes: return probe entry, prepare uretprobe Anton Arapov
2012-12-22 16:02 ` Oleg Nesterov
2012-12-21 11:16 ` [RFC PATCH 4/6] uretprobes: invoke return probe handlers Anton Arapov
2012-12-22 16:29 ` Oleg Nesterov [this message]
2012-12-21 11:16 ` [RFC PATCH 5/6] uprobes: add bp_vaddr argument to consumer handler Anton Arapov
2012-12-22 16:35 ` Oleg Nesterov
2012-12-22 17:13 ` Oleg Nesterov
2012-12-23 15:49 ` Oleg Nesterov
2013-01-08 14:27 ` Anton Arapov
2013-01-10 22:43 ` Josh Stone
2013-01-12 17:06 ` Oleg Nesterov
2013-01-15 19:15 ` Josh Stone
2013-01-16 16:20 ` Oleg Nesterov
2012-12-21 11:16 ` [RFC PATCH 6/6] uretprobes: register() and unregister() implementation Anton Arapov
2012-12-22 16:38 ` Oleg Nesterov
2012-12-21 17:37 ` [RFC PATCH 0/6] uprobes: return probe implementation Oleg Nesterov
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=20121222162924.GD18082@redhat.com \
--to=oleg@redhat.com \
--cc=anton@redhat.com \
--cc=fche@redhat.com \
--cc=jistone@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srikar@linux.vnet.ibm.com \
/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