[lkml]   [2013]   [Dec]   [10]   [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
(2013/12/11 0:28), Ingo Molnar wrote:
> * Masami Hiramatsu <> wrote:
>> (2013/12/05 19:21), Ingo Molnar wrote:
>>> * Masami Hiramatsu <> wrote:
>>>>> So we need both a maintainable and a sane/safe solution, and I'd
>>>>> like to apply the whole thing at once and be at ease that the
>>>>> solution is round. We should have done this years ago.
>>>> For the safeness of kprobes, I have an idea; introduce a whitelist
>>>> for dynamic events. AFAICS, the biggest unstable issue of kprobes
>>>> comes from putting *many* probes on the functions called from
>>>> tracers.
>>> If the number of 'noprobe' annotations is expected to explode then
>>> maybe another approach should be considered.
>> No, since this is a "quantitative" issue, the annotation helps us.

Sorry for confusion, it should be "the annotation helps us to solves
only for qualitative issue". It's my miss...

>>> For example in perf we detect recursion. Could kprobes do that and
>>> detect hitting a probe while running kprobes code, and ignore it [do
>>> an early return]?
>> Yes, the kprobe itself already has recursion detector and it rejects
>> calling handler.
> 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, 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.
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
This is the basic reason why the __kprobes annotation is introduced.

Thank you,

IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory

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