A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-11-07 02:59:16 -05:00
Code Issues Projects Releases Packages Wiki Activity
android_kernel_motorola_sm6375/fs/minix
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
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 <[email protected]>
Cc: Bodo Eggert <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
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 sendfile: remove .sendfile from filesystems that use generic_file_sendfile() 2007-07-10 08:04:13 +02:00
inode.c Slab API: remove useless ctor parameter and reorder parameters 2007-10-17 08:42:45 -07:00
itree_common.c [PATCH] Minix V3 support 2007-02-12 09:48:31 -08:00
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 [PATCH] mark struct inode_operations const 2 2007-02-12 09:48:46 -08:00