Ok, after mucho fruitless bisecting all I was able to figure out is that the bug is reproducable on stock 3.11+ kernels but _not_ on 3.11 kernel shipped with Ubuntu 13.10.