On Thu, 2015-05-14 at 11:34 +0800, Herbert Xu wrote:

On Wed, May 13, 2015 at 08:17:43PM -0700, Eric Dumazet wrote:

quoted

The initial bug report was on 3.18 for sure.

(Tester had to leave the program run ~8 hours to get the problem, on a 8
vCPU VM)

I can reproduce the bug quite easily (in a few seconds) on 4.0.3, I did
not spent lot of time trying 3.18, but it seems a bit harder.

No what I'm asking is on 3.18 was it permanent? I can imagine
there being a lookup bug in 3.18 that triggers during a rehash
but I cannot find any permanent corruption issues.

Let me try to reproduce this on 3.18.13. I'll give you an update.