tree ab41f3c567a5e94f3c0e500ab796ad3bdd38806c
parent 5ec8b75e3a2a94860ee99b5456fe1a963c8680e5
author Eric Sandeen <sandeen@redhat.com> 1224386880 -0700
committer Linus Torvalds <torvalds@linux-foundation.org> 1224517958 -0700

ext3: avoid printk floods in the face of directory corruption

A very large directory with many read failures (either due to storage
problems, or due to invalid size & blocks from corruption) will generate a
printk storm as the filesystem continues to try to read all the blocks.
This flood of messages can tie up the box until it is complete - which may
be a very long time, especially for very large corrupted values.

This is fixed by only reporting the corruption once each time we try to
read the directory.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: Eugene Teo <eugeneteo@kernel.sg>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>