)]}'
{
  "commit": "519deca0496a4df07d15acf3181ca5d573bffdec",
  "tree": "de86a407e1ea429fde16bc85d4587ebe4aa8194b",
  "parents": [
    "1930479c4b6bbcb6f164a5b3498e0d98329967f4"
  ],
  "author": {
    "name": "Aneesh Kumar K.V",
    "email": "aneesh.kumar@linux.vnet.ibm.com",
    "time": "Thu May 15 14:43:20 2008 -0400"
  },
  "committer": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Thu May 15 14:43:20 2008 -0400"
  },
  "message": "ext4: Retry block allocation if new blocks are allocated from system zone.\n\nIf the block allocator gets blocks out of system zone ext4 calls\next4_error. But if the file system is mounted with errors\u003dcontinue\nretry block allocation. We need to mark the system zone blocks as\nin use to make sure retry don\u0027t pick them again\n\nSystem zone is the block range mapping block bitmap, inode bitmap and inode\ntable.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "da994374ec3b2c6e13c103bf9e83b7dd87353edc",
      "old_mode": 33188,
      "old_path": "fs/ext4/balloc.c",
      "new_id": "30494c5da84303eb820cc5494b3f4fb2302f5e6a",
      "new_mode": 33188,
      "new_path": "fs/ext4/balloc.c"
    },
    {
      "type": "modify",
      "old_id": "1d7fde994521434271682c95ffd611991e287e7f",
      "old_mode": 33188,
      "old_path": "fs/ext4/mballoc.c",
      "new_id": "873ad9b3418ceeeb6b232566e525b60ccac07616",
      "new_mode": 33188,
      "new_path": "fs/ext4/mballoc.c"
    }
  ]
}