)]}'
{
  "commit": "2cac13e41bf5b99ffc426bd28dfd2248df1dfa67",
  "tree": "b74e7e863b7d7c2e116dc6754d8faf701c0aa3c9",
  "parents": [
    "6af021d8fc3bcce790e7fbb391e39c5920fa3f71"
  ],
  "author": {
    "name": "Liu Bo",
    "email": "liubo2009@cn.fujitsu.com",
    "time": "Thu Feb 09 18:17:41 2012 +0800"
  },
  "committer": {
    "name": "David Sterba",
    "email": "dsterba@suse.cz",
    "time": "Wed Feb 15 16:40:23 2012 +0100"
  },
  "message": "Btrfs: fix trim 0 bytes after a device delete\n\nA user reported a bug of btrfs\u0027s trim, that is we will trim 0 bytes\nafter a device delete.\n\nThe reproducer:\n\n$ mkfs.btrfs disk1\n$ mkfs.btrfs disk2\n$ mount disk1 /mnt\n$ fstrim -v /mnt\n$ btrfs device add disk2 /mnt\n$ btrfs device del disk1 /mnt\n$ fstrim -v /mnt\n\nThis is because after we delete the device, the block group may start from\na non-zero place, which will confuse trim to discard nothing.\n\nReported-by: Lutz Euler \u003clutz.euler@freenet.de\u003e\nSigned-off-by: Liu Bo \u003cliubo2009@cn.fujitsu.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "283af7a676a39b4c2f31d7d9b7caf81607eee4ea",
      "old_mode": 33188,
      "old_path": "fs/btrfs/extent-tree.c",
      "new_id": "60bfe2d68547b8f7a7fed66c6d41d75c6dd7daef",
      "new_mode": 33188,
      "new_path": "fs/btrfs/extent-tree.c"
    }
  ]
}