)]}'
{
  "commit": "c4b5a614316c505922a522b2e35ba05ea3e08a7c",
  "tree": "8b76988940551726ef05d311e02a06bb61464274",
  "parents": [
    "a9e817425dc0baede8ebe5fbc9984a640257432b"
  ],
  "author": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Fri Apr 24 18:45:35 2009 -0400"
  },
  "committer": {
    "name": "Theodore Ts\u0027o",
    "email": "tytso@mit.edu",
    "time": "Fri Apr 24 18:45:35 2009 -0400"
  },
  "message": "ext4: Do not try to validate extents on special files\n\nThe EXTENTS_FL flag should never be set on special files, but if it\nis, don\u0027t bother trying to validate that the extents tree is valid,\nsince only files, directories, and non-fast symlinks will ever have an\nextent data structure.  We perhaps should flag the filesystem as being\ncorrupted if we see a special file (named pipes, device nodes, Unix\ndomain sockets, etc.) with the EXTENTS_FL flag, but e2fsck doesn\u0027t\ncurrently check this case, so we\u0027ll just ignore this for now, since\nit\u0027s harmless.\n\nWithout this fix, a special device with the extents flag is flagged as\nan error by the kernel, so it is impossible to access or delete the\ninode, but e2fsck doesn\u0027t see it as a problem, leading to\nconfused/frustrated users.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "11460037ea9de61e4d923620f43e9721a30d0f44",
      "old_mode": 33188,
      "old_path": "fs/ext4/inode.c",
      "new_id": "e91f978c7f12848616855876628189a44a6885f8",
      "new_mode": 33188,
      "new_path": "fs/ext4/inode.c"
    }
  ]
}