)]}'
{
  "commit": "492a74f4210e15f4701422e2e1c4cd3c1e45ddae",
  "tree": "a45808e0aa8e5f50ca934a571660f24d6b2d8e1d",
  "parents": [
    "74bf4076f2ed79b5510440b72a561823a8852ec0"
  ],
  "author": {
    "name": "Steven Rostedt",
    "email": "srostedt@redhat.com",
    "time": "Mon Jan 25 15:17:47 2010 -0500"
  },
  "committer": {
    "name": "Steven Rostedt",
    "email": "rostedt@goodmis.org",
    "time": "Tue Jan 26 16:09:30 2010 -0500"
  },
  "message": "ring-buffer: Check if ring buffer iterator has stale data\n\nUsually reads of the ring buffer is performed by a single task.\nThere are two types of reads from the ring buffer.\n\nOne is a consuming read which will consume the entry that was read\nand the next read will be the entry that follows.\n\nThe other is an iterator that will let the user read the contents of\nthe ring buffer without modifying it. When an iterator is allocated,\nwrites to the ring buffer are disabled to protect the iterator.\n\nThe problem exists when consuming reads happen while an iterator is\nallocated. Specifically, the kind of read that swaps out an entire\npage (used by splice) and replaces it with a new read. If the iterator\nis on the page that is swapped out, then the next read may read\nfrom this swapped out page and return garbage.\n\nThis patch adds a check when reading the iterator to make sure that\nthe iterator contents are still valid. If a consuming read has taken\nplace, the iterator is reset.\n\nSigned-off-by: Steven Rostedt \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "edefe3b2801b746d794316eba5e2259fac8751af",
      "old_mode": 33188,
      "old_path": "kernel/trace/ring_buffer.c",
      "new_id": "503b630e0bda6fdd246bd50b47b9d4f652100aae",
      "new_mode": 33188,
      "new_path": "kernel/trace/ring_buffer.c"
    }
  ]
}