This article is more than slightly inaccurate, I'm afraid. (I'm the poor bloody reporter originally afflicted by this, though it seems it has hit someone else's USB key. I'd rather have a USB affected than my home directory, I must say, but one does not choose such things.)
- Ted did not 'bisect' the kernel to find the bug; he looked at the ext4-affecting patches in the affected range to find those that seemed suspicious. Indeed, presently his fix is based on an educated guess, and is not known to work (or not to work).
- The new patch is at least in part a *debugging* patch, and may or may not work: I have to get up the gumption to reboot into it and risk my home directory again before it's possible to say anything one way or the other.
There is definitely a bug; Ted may have fixed it; all further is unknown at present.
(The vicious attacks on various people for allowing this bug through are wholly unjustified. If this bug really does affect you only after multiple mounts, it's quite hard to spot in most regression test mechanisms, particularly given that the corruption only affects lightly-loaded, not heavily-loaded nor idle filesystems, and only seemingly a subset of those. It's a tricky bug. Bugs happen. No blame attaches.)