Comment 18 for bug 1215513

Thanks, I was experiencing the problem on precise 3.2.0-54.82 where it should also be applied. zram changes (including the one triggering the problem) got backported to 3.2 series in 3.2.49: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.49

This fix should eventully be applied upstream in 3.2.x as well as it was applied in 3.10.7 (where the bug commit appeared in 3.10.6): https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.7 .