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>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
adrian.m.negreanu@intel.com, Torsten.Polle@gmx.de
Subject: Re: [PATCH 5/7] uretprobes: return probe exit, invoke handlers
Date: Mon, 25 Mar 2013 17:38:00 +0100 [thread overview]
Message-ID: <20130325163800.GA8324@redhat.com> (raw)
In-Reply-To: <20130325154940.GA2178@bandura.brq.redhat.com>
On 03/25, Anton Arapov wrote:
>
> On Sun, Mar 24, 2013 at 05:28:17PM +0100, Oleg Nesterov wrote:
> >
> > Ignoring the fact you need put_uprobe/kfree, it seems that we should
> > do something like this,
> >
> > do {
> > handler_uretprobe_chain(...);
> >
> > if (!ri->dirty) // not chained
> > break;
> >
> > ri = ri->next;
> > } while (ri);
> >
> > utask->return_instances = ri;
> > No?
>
> Oleg, Do you mean
>
> do {
> handler_uretprobe_chain(...);
>
> ri = ri->next;
>
> if (!ri->dirty) // not chained
> break;
> } while (ri);
>
> utask->return_instances = ri;
>
> otherwise we stuck with the first instance in stack.
Not sure I understand... but it is very possible I missed something.
But the pseudo code I wrote is not correct, I meant
utask->return_instances = ri->next;
after the main loop.
> ...and perhaps for(;;) would be 'more beautiful' here?
Oh, I would not mind either way. In fact we do not really need
ri != NULL check inside the loop (again, unless I am confused).
We must see a non-chained entry in the stack unless we have a
bug.
Oleg.
next prev parent reply other threads:[~2013-03-25 16:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 13:08 [PATCH 0/7] uretprobes: return probes implementation Anton Arapov
2013-03-22 13:08 ` [PATCH 1/7] uretprobes: preparation patch Anton Arapov
2013-03-23 17:42 ` Oleg Nesterov
2013-03-22 13:08 ` [PATCH 2/7] uretprobes: extract fill_page() and trampoline implementation Anton Arapov
2013-03-24 14:41 ` Oleg Nesterov
2013-03-24 18:20 ` [PATCH 0/5] kmap cleanups for uretprobes (Was: extract fill_page() and trampoline implementation) Oleg Nesterov
2013-03-24 18:21 ` [PATCH 1/5] uprobes: Turn copy_opcode() into copy_from_page() Oleg Nesterov
2013-03-25 10:30 ` Anton Arapov
2013-03-26 11:59 ` Srikar Dronamraju
2013-03-24 18:21 ` [PATCH 2/5] uprobes: Change __copy_insn() to use copy_from_page() Oleg Nesterov
2013-03-25 10:31 ` Anton Arapov
2013-03-26 12:00 ` Srikar Dronamraju
2013-03-24 18:21 ` [PATCH 3/5] uprobes: Kill the unnecesary filp != NULL check in __copy_insn() Oleg Nesterov
2013-03-25 10:31 ` Anton Arapov
2013-03-26 12:00 ` Srikar Dronamraju
2013-03-24 18:21 ` [PATCH 4/5] uprobes: Introduce copy_to_page() Oleg Nesterov
2013-03-25 10:31 ` Anton Arapov
2013-03-26 12:02 ` Srikar Dronamraju
2013-03-24 18:21 ` [PATCH 5/5] uprobes: Change write_opcode() to use copy_*page() Oleg Nesterov
2013-03-25 10:31 ` Anton Arapov
2013-03-26 11:59 ` Srikar Dronamraju
2013-03-25 10:30 ` [PATCH 0/5] kmap cleanups for uretprobes (Was: extract fill_page() and trampoline implementation) Anton Arapov
2013-03-25 11:58 ` [PATCH 2/7] uretprobes: extract fill_page() and trampoline implementation Oleg Nesterov
2013-03-22 13:09 ` [PATCH 3/7] uretprobes/x86: hijack return address Anton Arapov
2013-03-24 14:59 ` Oleg Nesterov
2013-03-22 13:09 ` [PATCH 4/7] uretprobes: return probe entry, prepare_uretprobe() Anton Arapov
2013-03-22 15:02 ` Oleg Nesterov
2013-03-26 12:26 ` Anton Arapov
2013-03-26 14:34 ` Oleg Nesterov
2013-03-23 17:46 ` Oleg Nesterov
2013-03-24 15:26 ` Oleg Nesterov
2013-03-25 15:51 ` Anton Arapov
2013-03-26 8:45 ` Anton Arapov
2013-03-26 8:50 ` Anton Arapov
2013-03-22 13:09 ` [PATCH 5/7] uretprobes: return probe exit, invoke handlers Anton Arapov
2013-03-24 16:28 ` Oleg Nesterov
2013-03-25 12:31 ` Oleg Nesterov
2013-03-25 15:49 ` Anton Arapov
2013-03-25 16:38 ` Oleg Nesterov [this message]
2013-03-26 8:36 ` Anton Arapov
2013-03-22 13:09 ` [PATCH 6/7] uretprobes: limit the depth of return probe nestedness Anton Arapov
2013-03-24 16:54 ` Oleg Nesterov
2013-03-22 13:09 ` [PATCH 7/7] uretprobes: implemented, thus remove -ENOSYS Anton Arapov
2013-03-22 13:13 ` Anton Arapov
2013-03-22 13:09 ` [PATCH 7/7] uretprobes: remove -ENOSYS as return probes implemented Anton Arapov
2013-03-22 15:10 ` [PATCH 0/7] uretprobes: return probes implementation Oleg Nesterov
2013-03-22 21:40 ` Josh Stone
2013-03-23 6:43 ` Anton Arapov
2013-03-23 18:04 ` Oleg Nesterov
2013-03-23 17:56 ` 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=20130325163800.GA8324@redhat.com \
--to=oleg@redhat.com \
--cc=Torsten.Polle@gmx.de \
--cc=adrian.m.negreanu@intel.com \
--cc=ananth@in.ibm.com \
--cc=anton@redhat.com \
--cc=fche@redhat.com \
--cc=jistone@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).