)]}'
{
  "commit": "c4932dbe63dae2d23b4f596caa5d286ebfe042cf",
  "tree": "5fa02cc795112a45b20f4b5d279f70eb6834c9ba",
  "parents": [
    "e7c96e8e47baf263d93a8dbbebca7216a912ca05"
  ],
  "author": {
    "name": "boxi liu",
    "email": "boxi10liu@gmail.com",
    "time": "Mon Jul 01 08:12:37 2013 -0400"
  },
  "committer": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Mon Jul 01 08:12:37 2013 -0400"
  },
  "message": "ext4: improve free space calculation for inline_data\n\nIn ext4 feature inline_data,it use the xattr\u0027s space to store the\ninline data in inode.When we calculate the inline data as the xattr,we\nadd the pad.But in get_max_inline_xattr_value_size() function we count\nthe free space without pad.It cause some contents are moved to a block\neven if it can be\nstored in the inode.\n\nSigned-off-by: liulei \u003clewis.liulei@huawei.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Tao Ma \u003cboyu.mt@taobao.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "33331b4c21783b1e93169d9abef3e3e0441b5956",
      "old_mode": 33188,
      "old_path": "fs/ext4/inline.c",
      "new_id": "b8a07466144f62f837479b90431b26f793673797",
      "new_mode": 33188,
      "new_path": "fs/ext4/inline.c"
    }
  ]
}