Re: [PATCH 0/3] tracing/function-graph-tracer: signal interrupt triggering on output

[Ingo Molnar <mingo@elte.hu>]

* Frédéric Weisbecker <fweisbec@gmail.com> wrote:

> 2008/12/13 Ingo Molnar <mingo@elte.hu>:
> > Another thing, i just noticed that ftrace_print() is broken in certain
> > situations, for example a plain newline:
> >
> >        ftrace_printk("\n");
> >
> > printed via trace_pipe will print some weirdly concatenated line:
> >
> >           <...>-2994  [007]   406.498986: debug_show:          <...>-2994  [007]   406.498986:            <...>-2994  [007]   406.498986: debug_show:
> >
> > not via a separate, standalone, empty line.
> 
> I just tested with latest -tip and I don't any problem with it.
> With a single ftrace_printk("\n") on might_sleep() I get:
> 
>            <...>-2739  [000]   145.692153: __might_sleep:
>            <...>-2739  [000]   145.692155: __might_sleep:
>            <...>-2739  [000]   145.692157: __might_sleep:
>            <...>-2739  [000]   145.692158: __might_sleep:
> 
> with trace or trace_iter file.
> Does it always occur or in rare situations?

it seemed to occur all the time. Will investigate it if i see it again.

	Ingo