summaryrefslogtreecommitdiff
path: root/security/capability.c
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2009-02-17 10:58:41 -0500
committerGreg Kroah-Hartman <gregkh@suse.de>2009-02-20 14:37:19 -0800
commitd5f85db686df375bd39168bd0032c4be6863f35c (patch)
tree993d1700e81997cb1058cf094d890f51975842db /security/capability.c
parent235cda408948bb340b37340056e55ca13bd3137f (diff)
ext4: only use i_size_high for regular files
(cherry picked from commit 06a279d636734da32bb62dd2f7b0ade666f65d7c) Directories are not allowed to be bigger than 2GB, so don't use i_size_high for anything other than regular files. E2fsck should complain about these inodes, but the simplest thing to do for the kernel is to only use i_size_high for regular files. This prevents an intentially corrupted filesystem from causing the kernel to burn a huge amount of CPU and issuing error messages such as: EXT4-fs warning (device loop0): ext4_block_to_path: block 135090028 > max Thanks to David Maciejak from Fortinet's FortiGuard Global Security Research Team for reporting this issue. http://bugzilla.kernel.org/show_bug.cgi?id=12375 Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'security/capability.c')
0 files changed, 0 insertions, 0 deletions