Comment 132 for bug 330824

My git bisect is finished and revealed that commit dbf8b1c4e8122e705447b69aea9ee6ef3a9caa30 is the faulty one, confirming Carey Underwood previous results. Bisect log attached and commit diff attached.

Trying to revert that whole patch in current jaunty kernel makes it FTBFS so I could not test reverting the patch to re-confirm that it fixes the bug.

However, results are pretty definitive as this bug is VERY easy to reproduce on my laptop (2 seconds), and each git commit that I tested had to remove the same huge quantity of files without crashing to get a "git bisect good".