> Turns out this is really easy to reproduce. One process reads
> the eeprom over and over again, another runs i2cdump in a loop,
> and voila ... lots of corruptions. Scary, especially considering
> how wide-spread this kind of i2c access is in the kernel.

A coccinelle script should at least be able to find vulnerable code
paths, maybe even fix it. But not today for me... Thanks for testing and
sharing the results!