The problem is just in the disagreement between e2fsck and the kernel
over which is the right thing to do. We can fix it in either e2fsck
or the kernel, and neither is really any more correct than the other.
For what it's worth, I tend to think that the kernel can afford to be
a conservative here, so any change in the . or .. dirents is
reasonable cause for getting upset.
I've always been of the "be conservative in what you send, and liberal
in what you accept". So I'll be changing e2fsck to fix non-NULL
terminated directories, but I think it would also be good for the Kernel
to not require that . and .. be NULL-terminated.
- Ted