lkml.org 
[lkml]   [2013]   [Oct]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: FTRACE_WARN_ON((rec->flags & ~FTRACE_FL_MASK) == 0))
On Mon, Sep 30, 2013 at 11:56:06PM -0400, Steven Rostedt wrote:

> > Steve, any further thoughts on this ? I can't do more than a few hours of fuzz-testing
> > without eventually running into this.
>
> I'm currently traveling, but as it seems that you have a pretty good
> reproducer, can trace what trinity does up to the point it crashes?
>
> I think we can do that with other buffers. If you download the latest
> trace-cmd, you can run:
>
> trace-cmd record -e syscalls -B trinity trinity <args>
>
> This will create a ftrace sub buffer called trinity and shouldn't be
> affected by the other ftrace functions. Then it should trace all the
> syscalls that trinity does. I guess a strace could be used too.

It seems like trace-cmd needs to be run as root. all hell will break loose if trinity gets root privs.

Dave



\
 
 \ /
  Last update: 2013-10-01 07:01    [W:0.077 / U:1.908 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site