The current checksum routines appear to break on certain 2-byte aligned data.
This wasn't introduced by the latest change to checksum.S on the 27th of
June - it looks like it's been there for a while.
See attached testcase, which produces the following output:
Checksum of testcase at 8c110214 is 0x0 Checksum of testcase at 8c110215 is 0x0 Checksum of testcase at 8c110216 is 0x695a Checksum of testcase at 8c110217 is 0x695a Checksum of testcase at 8c110218 is 0x0
Now perhaps you can forgive it for getting the 8c110215 and 8c110217
versions wrong - I'm not sure other architectures will get that right
either. But the 8c110216 case should work.
--
dwmw2
|
