No doubt that this is something that you don't want in your stable tree, but saying that it will wipe out your filesystem is an exageration. All of the errors caused by this bug can be fixed by fsck.ext2. Also, the bug only occurs when filesystems are unmounted. Anyways, it's all moot now I guess since 2.4.16 is out.
