)]}'
{
  "commit": "637aff46f94a754207c80c8c64bf1b74f24b967d",
  "tree": "837fb3196236998c3c3ae44762ed3167ef0256f4",
  "parents": [
    "2f718ffc16c43a435d12919c75dbfad518abd056"
  ],
  "author": {
    "name": "Nick Piggin",
    "email": "npiggin@suse.de",
    "time": "Tue Oct 16 01:25:00 2007 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@woody.linux-foundation.org",
    "time": "Tue Oct 16 09:42:55 2007 -0700"
  },
  "message": "fs: fix data-loss on error\n\nNew buffers against uptodate pages are simply be marked uptodate, while the\nbuffer_new bit remains set.  This causes error-case code to zero out parts of\nthose buffers because it thinks they contain stale data: wrong, they are\nactually uptodate so this is a data loss situation.\n\nFix this by actually clearning buffer_new and marking the buffer dirty.  It\nmakes sense to always clear buffer_new before setting a buffer uptodate.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "09bb80c479d8b84a02d6defc7f70fef831bb6eb8",
      "old_mode": 33188,
      "old_path": "fs/buffer.c",
      "new_id": "9ece6c2086d0588c4a1e9f5bf276c5ca20df443d",
      "new_mode": 33188,
      "new_path": "fs/buffer.c"
    }
  ]
}