Thank you for the report.  The patch has been committed.
HEAD =>
4.2     => 4.2.1 next (likely 4.2.1b1)

The problem was added in 4.2 and so previous versions are not affected.