In anyway, this is most likely an upstream bug and should be reported to upstream (linux-i2c@vger.kernel.org).