why crc16_t10dif() may make mistakes but crc16_t10dif_copy() running OK in file storage test ?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start at the reported call chain hcrc_calc_csum16_inner -> crc16_t10dif -> crc16_t10dif_by16_10, and compare it with crc16_t10dif_copy() during the file-write test. Reproduce the CRC mismatch with a minimal case if possible, then determine whether the fault is in the API call or the surrounding storage operation and document the evidence.
Written by the indexing model from the issue text.
Description
Problem description
in our distributed file storage， we use isa-l crc as data validation in file storage io . to be sure, we use the API as follows:
crc16_t10dif()
however, in our test，the API return error, and some partial stack information is as follows:
(gdb) bt
#0 0x00000000004404f4 in crc16_t10dif_by16_10()
#1 0x00007fdef2d86377 in hcrc_calc_csum16_inner (...)
...
The calling relationship of functions is: hcrc_calc_csum16_inner -- > crc16_t10dif -- > crc16_t10dif_by16_10
and，there is crc bug happens when performing file write operations.
But when we switch crc16_t10dif to crc16_t10dif_copy(), the program is OK
What a strange thing ???
now， we have 2 ideas as follows:
(1). the function crc16_t10dif has mistakes itself when using it, but we have no idea how it happens, e.g compile optimization;
(2). running error in crc16_t10dif maybe has relationship with our file storage business or something , however， we can't catch it.
So, we want to know， if somebody has meet the same questions ? thanks a lot.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/isa-l
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
ISA-L Needs LZ4Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
bug intrinsic medium priority rt_lib
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
[CLI] Clarify distinction between 'capture camera' and 'capture screen' in help text and outputOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-vision#18 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
sumatrapdfreader/sumatrapdf#6417 · 3 comments ·
-
[BUG] Cython cache evicts most recent instead of oldest entry on cleanupPossibly taken @scoder claimed this today. OpenBuild System defect
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
HexaCluster/credcheck#94 ·