(2013/11/30 22:46), Ingo Molnar wrote:
Anyway, to fix all of them, I think we need file-based blacklist
especially for assembler symbols.
>>>
>>> assembler symbols shouldn't be particular hard either, just put them
>>> into the noprobes section.
>>
>> Would you mean .kprobes.text? Hmm, I
* Masami Hiramatsu wrote:
> (2013/11/27 22:30), Ingo Molnar wrote:
> >
> > * Masami Hiramatsu wrote:
> >
> >> (2013/11/22 11:35), Masami Hiramatsu wrote:
> >>> (2013/11/21 16:29), Ingo Molnar wrote:
>
> * Masami Hiramatsu wrote:
>
> > (2013/11/21 2:36), Frank Ch. Eigler wr
(2013/11/27 22:30), Ingo Molnar wrote:
>
> * Masami Hiramatsu wrote:
>
>> (2013/11/22 11:35), Masami Hiramatsu wrote:
>>> (2013/11/21 16:29), Ingo Molnar wrote:
* Masami Hiramatsu wrote:
> (2013/11/21 2:36), Frank Ch. Eigler wrote:
[ ... ]
>> one needs to resort
* Masami Hiramatsu wrote:
> (2013/11/22 11:35), Masami Hiramatsu wrote:
> > (2013/11/21 16:29), Ingo Molnar wrote:
> >>
> >> * Masami Hiramatsu wrote:
> >>
> >>> (2013/11/21 2:36), Frank Ch. Eigler wrote:
> >>
> >> [ ... ]
> one needs to resort to something like:
>
> # cat /proc/
(2013/11/22 11:35), Masami Hiramatsu wrote:
> (2013/11/21 16:29), Ingo Molnar wrote:
>>
>> * Masami Hiramatsu wrote:
>>
>>> (2013/11/21 2:36), Frank Ch. Eigler wrote:
>>
>> [ ... ]
one needs to resort to something like:
# cat /proc/kallsyms | grep ' [tT] ' | while read addr type sym
