kernel-fxtec-pro1x/fs/minix
Eric Sandeen f44ec6f3f8 limit minixfs printks on corrupted dir i_size
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>
2007-10-17 08:42:53 -07:00
..
bitmap.c fs: mark nibblemap const 2007-10-17 08:42:47 -07:00
dir.c minixfs: convert to new aops 2007-10-16 09:42:57 -07:00
file.c
inode.c Slab API: remove useless ctor parameter and reorder parameters 2007-10-17 08:42:45 -07:00
itree_common.c
itree_v1.c limit minixfs printks on corrupted dir i_size 2007-10-17 08:42:53 -07:00
itree_v2.c limit minixfs printks on corrupted dir i_size 2007-10-17 08:42:53 -07:00
Makefile
minix.h minixfs: convert to new aops 2007-10-16 09:42:57 -07:00
namei.c