)]}'
{
  "commit": "b4ca2b4b577c3530e34dcfaafccb2cc680ce95d1",
  "tree": "5145abc9aa66a7d466e40429780c7dfdcfedac84",
  "parents": [
    "10b3a32d292c21ea5b3ad5ca5975e88bb20b8d68"
  ],
  "author": {
    "name": "Joseph Qi",
    "email": "joseph.qi@huawei.com",
    "time": "Fri May 24 15:55:34 2013 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Fri May 24 16:22:52 2013 -0700"
  },
  "message": "ocfs2: goto out_unlock if ocfs2_get_clusters_nocache() failed in ocfs2_fiemap()\n\nLast time we found there is lock/unlock bug in ocfs2_file_aio_write, and\nthen we did a thorough search for all lock resources in\nocfs2_inode_info, including rw, inode and open lockres and found this\nbug.  My kernel version is 3.0.13, and it is also in the lastest version\n3.9.  In ocfs2_fiemap, once ocfs2_get_clusters_nocache failed, it should\ngoto out_unlock instead of out, because we need release buffer head, up\nread alloc sem and unlock inode.\n\nSigned-off-by: Joseph Qi \u003cjoseph.qi@huawei.com\u003e\nReviewed-by: Jie Liu \u003cjeff.liu@oracle.com\u003e\nCc: Mark Fasheh \u003cmfasheh@suse.com\u003e\nCc: Joel Becker \u003cjlbec@evilplan.org\u003e\nAcked-by: Sunil Mushran \u003csunil.mushran@gmail.com\u003e\nCc: \u003cstable@vger.kernel.org\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": "1c39efb71bab6d2c4926962c0a642d291e2b360b",
      "old_mode": 33188,
      "old_path": "fs/ocfs2/extent_map.c",
      "new_id": "2487116d0d3312981834aa3667fd708dc7aa05ab",
      "new_mode": 33188,
      "new_path": "fs/ocfs2/extent_map.c"
    }
  ]
}