kernel_optimize_test/fs/omfs
Bob Copeland 8800a044c7 omfs: sanity check cluster size
A corrupt filesystem could have a bad cluster size; this could result in
the filesystem allocating too much space for files if too large, or
getting stuck in omfs_allocate_block if too small.  The proper range is
1-8 blocks.

Reported-by: Eric Sesterhenn <snakebyte@gmx.de>
Signed-off-by: Bob Copeland <me@bobcopeland.com>
2010-07-10 14:38:11 -04:00
..
bitmap.c tree-wide: fix assorted typos all over the place 2009-12-04 15:39:55 +01:00
dir.c omfs: check bounds on block numbers before passing to sb_bread 2010-07-10 14:37:06 -04:00
file.c omfs: check bounds on block numbers before passing to sb_bread 2010-07-10 14:37:06 -04:00
inode.c omfs: sanity check cluster size 2010-07-10 14:38:11 -04:00
Kconfig fs/Kconfig: move omfs out 2009-01-22 13:15:58 +03:00
Makefile omfs: update kbuild to include OMFS 2008-07-26 12:00:05 -07:00
omfs_fs.h omfs: sanity check cluster size 2010-07-10 14:38:11 -04:00
omfs.h omfs: check bounds on block numbers before passing to sb_bread 2010-07-10 14:37:06 -04:00