stupid apps can DOS filesystem in case of corrupt files

GoogleCodeExporter commented 8 years ago

Some fuckwad apps (lets call them Shwoogle Pisspot, for lack of a more 
spiteful name) ignore even the most hardcore errors and simply keep 
rambling on even if you clearly told them that there is a fucking I/O 
error! While this by itself would be OK if it only created a lot of CPU 
load, it seems that this behavior blocks all other processes from 
accessing files. Even killing the offending process won't help, it stays 
in D state, and there is still no way to access any files anymore. Only 
killing fusecompress and remounting the filesystem helps.

Original issue reported on code.google.com by ulrich.h...@gmail.com on 3 Sep 2008 at 10:51

GoogleCodeExporter commented 8 years ago

>>> while True:
...   try: a.seek(b)
...   except: pass
...   try: a.read(4096)
...   except: pass
...   b += 4096

kills the filesystem. The seek() is important, without it everything is fine 
and 
dandy.

Original comment by ulrich.h...@gmail.com on 3 Sep 2008 at 11:24

GoogleCodeExporter commented 8 years ago

Well, that actually triggered a different bug (hopefully fixed in r66).

Even when I try very hard to break stuff I cannot reproduce the original bug 
any more
-> wontfix.

Original comment by ulrich.h...@gmail.com on 4 Sep 2008 at 9:28

Changed state: WontFix

andrinux / fusecompress

stupid apps can DOS filesystem in case of corrupt files #22