Actually the results from testing would be obvious and I should have pointed this out in a better way. As the patch mentioned in the fix only went into rc1 of 2.6.35 the previous kernels were not affected. So it is pretty clear that all 2.6.35 and 2.6.32.17 are affected and need the mentioned patch soon.
This has been gone into current upstream releases and now also into the stable update 2.6.32.17 as Greg had done the release before looking over the replies. We did that backporting early because Ted Tso was pushing for them and filesystem tests were showing some real and also severe problems with the current ext4. So the patches came from a branch of Ted which he keeps specifically for things that should get back to 2.6.32- According to Eric Sandeen the patch has been recently acked by Ted and should show up in upstream soon. As you saw it already was in linux-next and I hope Linus will pick that up soon. Depending on the timing upstream stable, too needs to either revert the offending patch and re-release or add the fix as soon as it gets out officially. I need to wait for the release of a security kernel, but then we will try to get fixed kernels uploaded as soon as possible. There are other process issues which will cause delays but for affected parties, the pre-proposed PPA would contain the fixes first. https://launchpad.net/~kernel-ppa/+archive/pre-proposed -- lvm2 hangs when creating snapshot, requires reboot to resolve https://bugs.launchpad.net/bugs/605551 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
