Ted, On Thu, 30 Oct 2014, Theodore Ts'o wrote: > On Thu, Oct 30, 2014 at 10:11:26PM +0100, Thomas Gleixner wrote: > > > > That's a way better explanation than what I saw in the commit logs and > > it actually maps to the observed traces and stackdumps. > > I can't speak for Jan, but I suspect he didn't realize that there was > a problem. The commit description in b34090e5e2 makes it clear that > the intent was a performance improvement, and not an attempt to fix a > potential deadlock bug. Indeed. The changelog does not look like a bug fix. That's why I was worried about Chris 'magic resolution' report. > The difference is that in this case, it seems that Chris and Kevin was > able to reproduce the problem reliably. (It also might be that the RT > patch kits widens the race window and makes it much more likely to > trigger.) We've seen that before. RT indeed makes race conditions more prominent by opening way more race windows than a mainline kernel ever does. But there is a caveat. With the recent per cpu assumptions RT might very well run into some completely not mainline relevant RT specific pitfalls. And that's becoming worse with every day that RT is out of tree. But that's a totally different story. Thanks again for your profound analysis of the issue at hand! tglx -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
