)]}'
{
  "commit": "090ffaa55dacea774af9ee378d09e47fb7cea9ff",
  "tree": "5482762609a8c2e3a312434eb7e997e5b72912f3",
  "parents": [
    "97d848365e603def43c69e160937f073bf9cf02e"
  ],
  "author": {
    "name": "Wendy Cheng",
    "email": "wcheng@redhat.com",
    "time": "Wed Jun 27 11:00:03 2007 -0400"
  },
  "committer": {
    "name": "Steven Whitehouse",
    "email": "swhiteho@redhat.com",
    "time": "Mon Jul 09 08:23:59 2007 +0100"
  },
  "message": "[GFS2] inode size inconsistency\n\nThis should have been part of the NFS patch #1 but somehow I missed it\nwhen packaging the patches. It is not a critical issue as the others (I\nhope). RHEL 5.1 31.el5 kernel runs fine without this change.\n\nOur truncate code is chopped into two parts, one for vfs inode changes\n(in vmtruncate()) and one of gfs inode (in gfs2_truncatei()). These two\noperatons are, unfortunately, not atomic. So it could happens that\nvmtruncate() succeeds (inode-\u003ei_size is changed) but gfs2_truncatei\nfails (say kernel temporarily out of memory). This would leave gfs inode\ni_di.di_size out of sync with vfs inode i_size. It will later confuse\ngfs2_commit_write() if a write is issued. Last time I checked, it will\ncause file corruption.\n\nSigned-off-by: S. Wendy Cheng \u003cwcheng@redhat.com\u003e\nSigned-off-by: Steven Whitehouse \u003cswhiteho@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "84051b997a43739f866e8b25adebe60904b9eb6c",
      "old_mode": 33188,
      "old_path": "fs/gfs2/ops_inode.c",
      "new_id": "911c115b5c6c29ecf16aabe087c2be507bb58f71",
      "new_mode": 33188,
      "new_path": "fs/gfs2/ops_inode.c"
    }
  ]
}