)]}'
{
  "commit": "06a279d636734da32bb62dd2f7b0ade666f65d7c",
  "tree": "e3fb1a899ea7a9d527ff0d8edf3ca23778321728",
  "parents": [
    "c225aa57ff4ffe715df4692676b77c815a337236"
  ],
  "author": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Sat Jan 17 18:41:37 2009 -0500"
  },
  "committer": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Sat Jan 17 18:41:37 2009 -0500"
  },
  "message": "ext4: only use i_size_high for regular files\n\nDirectories are not allowed to be bigger than 2GB, so don\u0027t use\ni_size_high for anything other than regular files.  E2fsck should\ncomplain about these inodes, but the simplest thing to do for the\nkernel is to only use i_size_high for regular files.\n\nThis prevents an intentially corrupted filesystem from causing the\nkernel to burn a huge amount of CPU and issuing error messages such\nas:\n\nEXT4-fs warning (device loop0): ext4_block_to_path: block 135090028 \u003e max\n\nThanks to David Maciejak from Fortinet\u0027s FortiGuard Global Security\nResearch Team for reporting this issue.\n\nhttp://bugzilla.kernel.org/show_bug.cgi?id\u003d12375\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: stable@kernel.org\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c668e4377d76027a87f95eb168d6e54b024a1a69",
      "old_mode": 33188,
      "old_path": "fs/ext4/ext4.h",
      "new_id": "aafc9eba1c25c8aace126bafc56e70d058695621",
      "new_mode": 33188,
      "new_path": "fs/ext4/ext4.h"
    },
    {
      "type": "modify",
      "old_id": "a6444cee0c7e086c4b76b6906011d11b32de7c7f",
      "old_mode": 33188,
      "old_path": "fs/ext4/inode.c",
      "new_id": "49484ba801c930c5100957b76cf01b012f0ba31b",
      "new_mode": 33188,
      "new_path": "fs/ext4/inode.c"
    }
  ]
}