Comment 148 for bug 330824

Saïvann,

Thanks for your willingness to work on this.

>However the good news is that I'm ready to take a lot more time on this. If it requires me to
>git bisect again the whole jaunty kernel and to apply commit dbf8b1c4 each time I test one
>commit, I'm ready to do it. If you can only guide me about what is the best method to
>continue and find the information you need, I'll be overjoy to play again with this.

Actually, I have a better, more efficient way of doing this. I've updated the "ubuntu-330824-test" branch on the ext4.git and my ext4 github repositories to include the rest of the Ubuntu Sauce patches up to dbf8b1c4. That is, I started with the ubuntu-330824-test branch which you tested, and then I create a script which cherry-picked all of the non-ext4 commits from the Ubuntu kernel branch onto the ubuntu-330824-test branch. So right now, the contents of ubuntu-330824-test and the Ubuntu sauce patch up to dbf8b1c4 are identical; that is, if you were to do a "git diff ubuntu-330824-test dbf8b1c4" you would get no output indicating there is no difference between these these two branches. The difference is that in the ubuntu-330824-test then ten ext4 patches were moved to the beginning of the patch series. So if you test the tip of ubuntu-330824-test, you should see a failure, since that tree is identical to tree pointed to by the commit dbf8b1c4. However, if you bisect this git branch, you will hopefully find the other commit(s) that are required to trigger the bug.

Does that make sense?