)]}'
{
  "commit": "4b2286c3ef8317239ed5290f381970c14d8b3fe9",
  "tree": "e7ad23ce0e1c914990a5bf2eacaa90813e8838ff",
  "parents": [
    "ce0acec384c8b9cd3859291362272107c24fb20e"
  ],
  "author": {
    "name": "Steven Rostedt (Google)",
    "email": "rostedt@goodmis.org",
    "time": "Mon Jan 08 12:34:20 2024 -0500"
  },
  "committer": {
    "name": "Steven Rostedt (Google)",
    "email": "rostedt@goodmis.org",
    "time": "Mon Jan 08 15:10:48 2024 -0500"
  },
  "message": "kbuffer: Always walk the events to calculate timestamp in kbuffer_read_buffer()\n\nIf the buffer to read the kbuffer subbuffer is big enough to hold the\nentire buffer, it was simply copied. But this is not good enough, as the\nnext read should include the events after what was copied. That means the\ntimestamps need to be calculated.\n\nJust copying the data is not enough as the timestamp of any event is an\noffset of the previous event. To know the event timestamp after what was\ncopied, the timestamps of the events before it need to be read, to know\nwhat the offset is against of the following event.\n\nLink: https://lore.kernel.org/linux-trace-devel/ZZwFvyGvm0C38eBh@google.com/\nLink: https://lore.kernel.org/linux-trace-devel/20240108123420.5e227075@gandalf.local.home\n\nFixes: 05821189 (\"kbuffer: Add kbuffer_read_buffer()\")\nReported-by: Vincent Donnefort \u003cvdonnefort@google.com\u003e\nSigned-off-by: Steven Rostedt (Google) \u003crostedt@goodmis.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d43fe5d972fd06d5743a4ae38ded7daaaca4c6c0",
      "old_mode": 33188,
      "old_path": "src/kbuffer-parse.c",
      "new_id": "691d53678f5f385075532059d7c2f37cdf370801",
      "new_mode": 33188,
      "new_path": "src/kbuffer-parse.c"
    }
  ]
}