)]}'
{
  "commit": "580be0837a7a59b207c3d5c661d044d8dd0a6a30",
  "tree": "4a659c92ed738367c1ed4d9b1b50fe018f401b81",
  "parents": [
    "5be461657be65460ad92be3527e3bb1dd11c49ea"
  ],
  "author": {
    "name": "Jan Kara",
    "email": "jack@suse.cz",
    "time": "Mon Sep 21 17:01:06 2009 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Tue Sep 22 07:17:24 2009 -0700"
  },
  "message": "fs: make sure data stored into inode is properly seen before unlocking new inode\n\nIn theory it could happen that on one CPU we initialize a new inode but\nclearing of I_NEW | I_LOCK gets reordered before some of the\ninitialization.  Thus on another CPU we return not fully uptodate inode\nfrom iget_locked().\n\nThis seems to fix a corruption issue on ext3 mounted over NFS.\n\n[akpm@linux-foundation.org: add some commentary]\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nCc: Christoph Hellwig \u003chch@infradead.org\u003e\nCc: \u003cstable@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": "b2ba83d2c4e12425629ed3681f2d2ca2d147f2e1",
      "old_mode": 33188,
      "old_path": "fs/inode.c",
      "new_id": "798052f87035e65ee21de37a916db35dd3b4a2e0",
      "new_mode": 33188,
      "new_path": "fs/inode.c"
    }
  ]
}