)]}'
{
  "commit": "e8a80c6f769dd4622d8b211b398452158ee60c0b",
  "tree": "e538f674c219d98d8829d6286aa9be6feee16c93",
  "parents": [
    "dd9c1549edef02290edced639f67b54a25abbe0e"
  ],
  "author": {
    "name": "Josh Hunt",
    "email": "johunt@akamai.com",
    "time": "Thu Feb 24 11:48:22 2011 +0100"
  },
  "committer": {
    "name": "Jan Kara",
    "email": "jack@suse.cz",
    "time": "Wed Mar 02 11:03:52 2011 +0100"
  },
  "message": "ext2: Fix link count corruption under heavy link+rename load\n\nvfs_rename_other() does not lock renamed inode with i_mutex. Thus changing\ni_nlink in a non-atomic manner (which happens in ext2_rename()) can corrupt\nit as reported and analyzed by Josh.\n\nIn fact, there is no good reason to mess with i_nlink of the moved file.\nWe did it presumably to simulate linking into the new directory and unlinking\nfrom an old one. But the practical effect of this is disputable because fsck\ncan possibly treat file as being properly linked into both directories without\nwriting any error which is confusing. So we just stop increment-decrement\ngames with i_nlink which also fixes the corruption.\n\nCC: stable@kernel.org\nCC: Al Viro \u003cviro@ZenIV.linux.org.uk\u003e\nSigned-off-by: Josh Hunt \u003cjohunt@akamai.com\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2e1d8341d827b173b44b4f034106a7db7f2be8da",
      "old_mode": 33188,
      "old_path": "fs/ext2/namei.c",
      "new_id": "adb91855ccd092c86f220161c922873bee7fce0c",
      "new_mode": 33188,
      "new_path": "fs/ext2/namei.c"
    }
  ]
}