)]}'
{
  "commit": "4e0bc3f3cd9028d4a2bc2f21c6d371b2f671823b",
  "tree": "511d96edb6c4f61d805b0daea755929e569b0714",
  "parents": [
    "5e23efd0c1d6c67761f859c141ba67bac80b81e0"
  ],
  "author": {
    "name": "Tao Ma",
    "email": "boyu.mt@taobao.com",
    "time": "Mon May 28 18:20:59 2012 -0400"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@linuxfoundation.org",
    "time": "Thu Feb 20 10:45:32 2014 -0800"
  },
  "message": "ext4: protect group inode free counting with group lock\n\ncommit 6f2e9f0e7d795214b9cf5a47724a273b705fd113 upstream.\n\nNow when we set the group inode free count, we don\u0027t have a proper\ngroup lock so that multiple threads may decrease the inode free\ncount at the same time. And e2fsck will complain something like:\n\nFree inodes count wrong for group #1 (1, counted\u003d0).\nFix? no\n\nFree inodes count wrong for group #2 (3, counted\u003d0).\nFix? no\n\nDirectories count wrong for group #2 (780, counted\u003d779).\nFix? no\n\nFree inodes count wrong for group #3 (2272, counted\u003d2273).\nFix? no\n\nSo this patch try to protect it with the ext4_lock_group.\n\nbtw, it is found by xfstests test case 269 and the volume is\nmkfsed with the parameter\n\"-O ^resize_inode,^uninit_bg,extent,meta_bg,flex_bg,ext_attr\"\nand I have run it 100 times and the error in e2fsck doesn\u0027t\nshow up again.\n\nSigned-off-by: Tao Ma \u003cboyu.mt@taobao.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Benjamin LaHaise \u003cbcrl@kvack.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@linuxfoundation.org\u003e\n\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b1c3f2ade2b0963e960acfff1aa69effe93cb88f",
      "old_mode": 33188,
      "old_path": "fs/ext4/ialloc.c",
      "new_id": "75c4f36bced8cba2216d182f3c22f00e168259c3",
      "new_mode": 33188,
      "new_path": "fs/ext4/ialloc.c"
    }
  ]
}