Comment 4 for bug 1779678

I've been running a 4.18 kernel for a long time now and I haven't been able to reproduce the bug. Please note however, that this bug was a race. Meaning, it is easily possible that the race has just gotten so unlikely that it doesn't matter anymore. I doubt it however, since a) there's a proper explanation for the prior bug and b) the locking has changed completely upstream.