diff options
author | 2009-04-24 18:45:35 -0400 | |
---|---|---|
committer | 2009-04-24 18:45:35 -0400 | |
commit | c4b5a614316c505922a522b2e35ba05ea3e08a7c (patch) | |
tree | 8b76988940551726ef05d311e02a06bb61464274 /include | |
parent | ext4: Ignore i_file_acl_high unless EXT4_FEATURE_INCOMPAT_64BIT is present (diff) | |
download | wireguard-linux-c4b5a614316c505922a522b2e35ba05ea3e08a7c.tar.xz wireguard-linux-c4b5a614316c505922a522b2e35ba05ea3e08a7c.zip |
ext4: Do not try to validate extents on special files
The EXTENTS_FL flag should never be set on special files, but if it
is, don't bother trying to validate that the extents tree is valid,
since only files, directories, and non-fast symlinks will ever have an
extent data structure. We perhaps should flag the filesystem as being
corrupted if we see a special file (named pipes, device nodes, Unix
domain sockets, etc.) with the EXTENTS_FL flag, but e2fsck doesn't
currently check this case, so we'll just ignore this for now, since
it's harmless.
Without this fix, a special device with the extents flag is flagged as
an error by the kernel, so it is impossible to access or delete the
inode, but e2fsck doesn't see it as a problem, leading to
confused/frustrated users.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions