[lkml]   [2013]   [Dec]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH -tip v4 0/6] kprobes: introduce NOKPROBE_SYMBOL() and fixes crash bugs

* Masami Hiramatsu <> wrote:

> > So why are annotations needed at all? What can happen if an
> > annotation is missing and a piece of code is probed which is also
> > used by the kprobes code internally - do we crash, lock up,
> > misbehave or handle it safely?
> The kprobe has recursion detector, [...]

It's the 'current_kprobe' percpu variable, checked via
kprobe_running(), right?

> [...] but it is detected in the kprobe exception(int3) handler, this
> means that if we put a probe before detecting the recursion, we'll
> do an infinite recursion.

So only the (presumably rather narrow) code path leading to the
recursion detection code has to be annotated, correct?

> And also, even if we can detect the recursion, we can't stop the
> kernel, we need to skip the probe. This means that we need to
> recover to the main execution path by doing single step. As you may
> know, since the single stepping involves the debug exception, we
> have to avoid proving on that path too. Or we'll have an infinite
> recursion again.

I don't see why this is needed: if a "probing is disabled" recursion
flag is set the moment the first probe fires, and if it's only cleared
once all processing is finished, then any intermediate probes should
simply return early from int3 and not fire.

What am I missing?



 \ /
  Last update: 2013-12-11 15:01    [W:0.075 / U:1.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site