This bug fix applies to both 2.6.31 and 2.6.32.Christoph did the hard work of catching/testing it, thanks!