minixfs: limit minixfs printks on corrupted dir i_size (CVE-2006-6058)
commit59531fe84bf82bdc2abc9b688919552c0bec1d47
authorEric Sandeen <sandeen@redhat.com>
Wed, 17 Oct 2007 06:27:15 +0000 (16 23:27 -0700)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 5 Nov 2007 17:56:07 +0000 (5 09:56 -0800)
tree6ed5cea73122865b8de746c42af85dd8cc8e0221
parentb67e7778425404c0261e5df2a04e41ae93a261f1
minixfs: limit minixfs printks on corrupted dir i_size (CVE-2006-6058)

patch 44ec6f3f89889a469773b1fd894f8fcc07c29cf in mainline

This attempts to address CVE-2006-6058
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6058

first reported at http://projects.info-pull.com/mokb/MOKB-17-11-2006.html

Essentially a corrupted minix dir inode reporting a very large
i_size will loop for a very long time in minix_readdir, minix_find_entry,
etc, because on EIO they just move on to try the next page.  This is
under the BKL, printk-storming as well.  This can lock up the machine
for a very long time.  Simply ratelimiting the printks gets things back
under control.  Make the message a bit more informative while we're here.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Cc: Bodo Eggert <7eggert@gmx.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
fs/minix/itree_v1.c
fs/minix/itree_v2.c