ISSUE SUMMARY
In standalone WiredTiger builds on big-endian systems that lack hardware CRC32c support, the incorrect software CRC32c functions are called.
USER IMPACT
This change does not impact any MongoDB user.
WORKAROUNDS
There is currently no workaround for this issue.
AFFECTED VERSIONS
This issue does not impact MongoDB production releases.
FIX VERSION
WiredTiger 3.1.1.
RESOLUTION DETAILS
This issue is only for standalone WiredTiger builds, there is no impact to MongoDB.
In order to uncover more race condition issues, we decided to run some jobs on PPC & zSeries machines, which have relaxed memory model or slow I/O channels. After switching wiredtiger-test-spinlock job onto zSeries, the 1st run captured below checksum mismatch error.
http://build.wiredtiger.com:8080/job/wiredtiger-test-spinlock/4571/
+ ../configure CFLAGS=-ggdb --enable-python --with-spinlock=gcc --enable-strict --with-berkeleydb=none checking for a BSD-compatible install... /bin/install -c checking whether build environment is sane... yes (...) ../../../build_posix/gnu-support/test-driver: line 95: 23533 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test_wt2695_checksum (...) test_wt2695_checksum: FAILED: check/40: hw == sw ? 0 : 1: known string #1: software checksum mismatch of 9 bytes: 0x10065321 != 0xe3069283 : Operation not permitted process aborting
It deserves an investigation to see if it's a legitimate problem.
- is caused by
-
WT-4179 Expose WiredTiger crc32c functions
-
- Closed
-