On Tue, Sep 13, 2011 at 04:58:13PM -0500, Alex Elder wrote:
> > Reviewed-by: Alex Elder <aelder at sgi.com>
>> Nevermind--the latest code doesn't look quite
> like that and doesn't suffer the same problem.
It needs to go into 3.1, where this bug was introduced. In the
3.2 queue it already has been fixed by different means