It looks like there are already several variations on this bug filed with upstream, though its surprising that it's present both in the 2.6 and 3.2/3.3 series.
It looks like there are already several variations on this bug filed with upstream, though its surprising that it's present both in the 2.6 and 3.2/3.3 series.