Greg091 commented 5 years ago

ISSUE:

Environment Information

PMDK package version(s): 1.6-352-g7e4312dd5
OS(es) version(s): Fedora30
ndctl version(s): 65
kernel version(s): 5.1.17-300.fc30.x86_64

Please provide a reproduction of the bug:

$ ./RUNTESTS ex_libpmemobj -s TEST20 -m force-enable

How often bug is revealed: (always, often, rare): always

Actual behavior:

$ ./RUNTESTS ex_libpmemobj -s TEST20 -m force-enable
ex_libpmemobj/TEST20: SETUP (check/pmem/debug/memcheck)
ex_libpmemobj/TEST20 failed with Valgrind. See memcheck20.log. Last 20 lines below.
ex_libpmemobj/TEST20 memcheck20.log ==85992==    by 0x4889B99: pmemobj_persist (obj.c:2711)
ex_libpmemobj/TEST20 memcheck20.log ==85992==    by 0x1099C5: realloc_int (array.c:244)
ex_libpmemobj/TEST20 memcheck20.log ==85992==    by 0x10A33D: do_realloc (array.c:447)
ex_libpmemobj/TEST20 memcheck20.log ==85992==    by 0x10A6AE: main (array.c:523)
ex_libpmemobj/TEST20 memcheck20.log ==85992==  Address 0x59c15c0 is in a rw- mapped file /mnt/mem/test_ex_libpmemobj20🟟⠏⠍⠙⠅ɗPMDKӜ⥺🟟/testfile segment
ex_libpmemobj/TEST20 memcheck20.log ==85992== 
ex_libpmemobj/TEST20 memcheck20.log ==85992== 
ex_libpmemobj/TEST20 memcheck20.log ==85992== HEAP SUMMARY:
ex_libpmemobj/TEST20 memcheck20.log ==85992==     in use at exit: 552 bytes in 1 blocks
ex_libpmemobj/TEST20 memcheck20.log ==85992==   total heap usage: 37,339 allocs, 37,303 frees, 60,411,462 bytes allocated
ex_libpmemobj/TEST20 memcheck20.log ==85992== 
ex_libpmemobj/TEST20 memcheck20.log ==85992== LEAK SUMMARY:
ex_libpmemobj/TEST20 memcheck20.log ==85992==    definitely lost: 0 bytes in 0 blocks
ex_libpmemobj/TEST20 memcheck20.log ==85992==    indirectly lost: 0 bytes in 0 blocks
ex_libpmemobj/TEST20 memcheck20.log ==85992==      possibly lost: 0 bytes in 0 blocks
ex_libpmemobj/TEST20 memcheck20.log ==85992==    still reachable: 0 bytes in 0 blocks
ex_libpmemobj/TEST20 memcheck20.log ==85992==         suppressed: 552 bytes in 1 blocks
ex_libpmemobj/TEST20 memcheck20.log ==85992== 
ex_libpmemobj/TEST20 memcheck20.log ==85992== For lists of detected and suppressed errors, rerun with: -s
ex_libpmemobj/TEST20 memcheck20.log ==85992== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
RUNTESTS: stopping: ex_libpmemobj/TEST20 failed, TEST=check FS=pmem BUILD=debug

Expected behavior:

Test should pass.

Details

Logs: memcheck20.log out20.log pmem20.log pmemobj20.log

Additional information about Priority and Help Requested:

Are you willing to submit a pull request with a proposed change? (Yes, No)

Requested priority: (Showstopper, High, Medium, Low)

janekmi commented 5 years ago

==72485== Unaddressable byte(s) found during client check request
==72485==    at 0x48C4396: pmem_flush (pmem.c:243)
==72485==    by 0x48C4418: pmem_persist (pmem.c:256)
==72485==    by 0x487FD7B: obj_norep_persist (obj.c:482)
==72485==    by 0x4885F55: pmemops_xpersist (pmemops.h:80)
==72485==    by 0x4885F55: pmemops_persist (pmemops.h:86)
==72485==    by 0x4885F55: pmemobj_persist (obj.c:2711)
==72485==    by 0x4018DC: realloc_int (array.c:244)
==72485==    by 0x402103: do_realloc (array.c:447)
==72485==    by 0x40240E: main (array.c:523)
==72485==  Address 0x59c15c0 is in a rw- mapped file /mnt/mem/test_ex_libpmemobj20😘⠏⠍⠙⠅ɗPMDKӜ⥺🙋/testfile segment