)]}'
{
  "commit": "8ae516aa8b8161254d3e402b3348b2a9b8d1efd0",
  "tree": "532a8665fb0a60fb62a0a27656a00d8829454cd1",
  "parents": [
    "4f9e5df211a8591b3fb5c154ecc7ec5d4ecd6b79",
    "8a56d7761d2d041ae5e8215d20b4167d8aa93f51"
  ],
  "author": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Tue Nov 26 18:04:21 2013 -0800"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Tue Nov 26 18:04:21 2013 -0800"
  },
  "message": "Merge tag \u0027trace-fixes-v3.13-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace\n\nPull tracing fixes from Steven Rostedt:\n \"This includes two fixes.\n\n  1) is a bug fix that happens when root does the following:\n\n     echo function_graph \u003e current_tracer\n     modprobe foo\n     echo nop \u003e current_tracer\n\n   This causes the ftrace internal accounting to get screwed up and\n   crashes ftrace, preventing the user from using the function tracer\n   after that.\n\n  2) if a TRACE_EVENT has a string field, and NULL is given for it.\n\n   The internal trace event code does a strlen() and strcpy() on the\n   source of field.  If it is NULL it causes the system to oops.\n\n   This bug has been there since 2.6.31, but no TRACE_EVENT ever passed\n   in a NULL to the string field, until now\"\n\n* tag \u0027trace-fixes-v3.13-rc1\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:\n  ftrace: Fix function graph with loading of modules\n  tracing: Allow events to have NULL strings\n",
  "tree_diff": []
}
