)]}'
{
  "commit": "3b2775942d6ccb14342f3aae55f22fbbfea8db14",
  "tree": "b17632b7df40dc9892eb3a562b0eaa385143a808",
  "parents": [
    "7c2ec3f0730729f4829d01f7c19538d135f86712"
  ],
  "author": {
    "name": "Liu Bo",
    "email": "bo.li.liu@oracle.com",
    "time": "Fri Mar 15 08:46:39 2013 -0600"
  },
  "committer": {
    "name": "Chris Mason",
    "email": "chris.mason@fusionio.com",
    "time": "Fri Mar 15 21:51:49 2013 -0400"
  },
  "message": "Btrfs: fix warning of free_extent_map\n\nUsers report that an extent map\u0027s list is still linked when it\u0027s actually\ngoing to be freed from cache.\n\nThe story is that\n\na) when we\u0027re going to drop an extent map and may split this large one into\nsmaller ems, and if this large one is flagged as EXTENT_FLAG_LOGGING which means\nthat it\u0027s on the list to be logged, then the smaller ems split from it will also\nbe flagged as EXTENT_FLAG_LOGGING, and this is _not_ expected.\n\nb) we\u0027ll keep ems from unlinking the list and freeing when they are flagged with\nEXTENT_FLAG_LOGGING, because the log code holds one reference.\n\nThe end result is the warning, but the truth is that we set the flag\nEXTENT_FLAG_LOGGING only during fsync.\n\nSo clear flag EXTENT_FLAG_LOGGING for extent maps split from a large one.\n\nReported-by: Johannes Hirte \u003cjohannes.hirte@fem.tu-ilmenau.de\u003e\nReported-by: Darrick J. Wong \u003cdarrick.wong@oracle.com\u003e\nSigned-off-by: Liu Bo \u003cbo.li.liu@oracle.com\u003e\nSigned-off-by: Chris Mason \u003cchris.mason@fusionio.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "83c790d840381dbb9f15ea7f2b8d7ed0221e6901",
      "old_mode": 33188,
      "old_path": "fs/btrfs/file.c",
      "new_id": "7bdb47faa12ed7a024bf014d33c46e88ce9f43ac",
      "new_mode": 33188,
      "new_path": "fs/btrfs/file.c"
    }
  ]
}