)]}'
{
  "commit": "d696b58ca2c3ca76e784ef89a7e0453d9b7ab187",
  "tree": "e5f02a13dc8fdec22e9223189122e5938e9ce77e",
  "parents": [
    "e0a413f619ef8bc366dafc6f8221674993b8d85f"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Thu Sep 22 11:50:27 2011 -0400"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Tue Oct 11 09:13:53 2011 -0400"
  },
  "message": "tracing: Do not allocate buffer for trace_marker\n\nWhen doing intense tracing, the kmalloc inside trace_marker can\nintroduce side effects to what is being traced.\n\nAs trace_marker() is used by userspace to inject data into the\nkernel ring buffer, it needs to do so with the least amount\nof intrusion to the operations of the kernel or the user space\napplication.\n\nAs the ring buffer is designed to write directly into the buffer\nwithout the need to make a temporary buffer, and userspace already\nwent through the hassle of knowing how big the write will be,\nwe can simply pin the userspace pages and write the data directly\ninto the buffer. This improves the impact of tracing via trace_marker\ntremendously!\n\nThanks to Peter Zijlstra and Thomas Gleixner for pointing out the\nuse of get_user_pages_fast() and kmap_atomic().\n\nSuggested-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nSuggested-by: Peter Zijlstra \u003ca.p.zijlstra@chello.nl\u003e\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "13f2b8472fed2a3b1a52d53adba43c33bb889cc5",
      "old_mode": 33188,
      "old_path": "kernel/trace/trace.c",
      "new_id": "f86efe90ca457c32c90ec6df7b98a586eee69be0",
      "new_mode": 33188,
      "new_path": "kernel/trace/trace.c"
    }
  ]
}