Bug #7828
openUnexpected remove behavior in util-hash
Description
In util-hash.c I have observed some behavior that is unexpected and likely incorrect. To see this behavior, create a hash table 32 entries wide and use the default hash function. Then add a short string “abc”, observe the string is stored properly. Now remove a string “iln”, and observe string “abc” is no longer in the table.
Other scenarios can provoke this behavior but this is possibly the simplest way. It occurs because if the table slot has one entry, remove does not perform a compare before removal.
I have a unit test patch to show this, and a fix patch to make it behave as a typical hash table would behave. The behavior goes back to at least 6.0 and continues into the current 8.0.1 work branch.
I am working on a PR now.
Updated by Philippe Antoine 9 days ago
- Related to Bug #7475: Problem in HashTable remove function added
Updated by Juliana Fajardini Reichow 8 days ago
PR for review: https://github.com/OISF/suricata/pull/13633
Updated by Juliana Fajardini Reichow 8 days ago
- Assignee changed from OISF Dev to Charles Vigue
Assigning to the author as there's already a PR :)
Updated by Charles Vigue 8 days ago
PR is here: https://github.com/OISF/suricata/pull/13639
Updated by Shivani Bhardwaj 8 days ago
- Related to deleted (Bug #7475: Problem in HashTable remove function)
Updated by Shivani Bhardwaj 8 days ago
- Has duplicate Bug #7475: Problem in HashTable remove function added