Searched hist:"55 ad63bf3a30936aced50f13452735c2f58b234c" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/fs/ext4/ |
| H A D | extents.c | diff 55ad63bf3a30936aced50f13452735c2f58b234c Fri Aug 28 09:40:33 CDT 2009 Theodore Ts'o <tytso@mit.edu> ext4: fix extent sanity checking code with AGGRESSIVE_TEST
The extents sanity-checking code depends on the ext4_ext_space_*()
functions returning the maximum alloable size for eh_max; however,
when the debugging #ifdef AGGRESSIVE_TEST is enabled to test the
extent tree handling code, this prevents a normally created ext4
filesystem from being mounted with the errors:
Aug 26 15:43:50 bsd086 kernel: [ 96.070277] EXT4-fs error (device sda8): ext4_ext_check_inode: bad header/extent in inode #8: too large eh_max - magic f30a, entries 1, max 4(3), depth 0(0)
Aug 26 15:43:50 bsd086 kernel: [ 96.070526] EXT4-fs (sda8): no journal found
Bug reported by Akira Fujita.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
|