You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pmemobj_free sets the PMEMoid object to NULL when freeing objects.
With the current design of storing the offset in hashtable->table_off, the offset is never set to null, and so a crash can cause a double-free to occur.
Thanks for the report. Let me get back to you after checking and fixing it. However, if you already have a solution, I would appreciate it if you make a pull request for it.
I'd be happy to submit a PR for this in the near future, but I will be slightly delayed by an upcoming deadline. I'll ping this issue once I have a solution or if I have any issues in coming up with one.
Bug
Exposed by crashing after freeing the hash table in
clht_gc_free
.RECIPE/P-CLHT/src/clht_gc.c
Lines 239 to 242 in fc508dd
pmemobj_free
sets the PMEMoid object to NULL when freeing objects.hashtable->table_off
, the offset is never set to null, and so a crash can cause a double-free to occur.Steps to reproduce
Will output something like:
The text was updated successfully, but these errors were encountered: