Prev: [PATCH] Fix uninitialized variable warning in do_one_initcall
Next: [PATCH] omfs: fix memory leak
From: Daniel Taylor on 3 Jul 2010 22:00
We're getting the following error with an EXT3 file sytem that
has 64K blocks (2.6.32.12, on a powerpc), although I don't see
any fixes for later kernels in a diff against 2.6.35-rc3):

ext3_readdir: bad entry in directory #11: rec_len is smaller than minimal -
offset=0, inode=0, rec_len=0, name_len=0

That message is generated in fs/ext3/dir.c:ext3_check_dir_entry()
when called from fs/ext3/dir.c:ext3_readdir(), AFAICT.

Did something get missed when EXT* handling for 64K blocks was
implemented or when a new feature was added?

Dan Taylor
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH] Fix uninitialized variable warning in do_one_initcall
Next: [PATCH] omfs: fix memory leak