Closed terofinn closed 2 years ago
The jool's pool4 db flush seem to always crash
When you say "always," you mean even when there's nothing in the table?
And if not, do you have a sample population add/remove/flush sequence?
Ok, I think I found the bug: Line 60 or 62 deletes the parent, then lines 68-69 attempt to dereference it. Duh.
I suppose I could fix it, but support for kernels 3.11- was abandoned a long time ago, so the right solution is to drop rbtree_foreach()
in favor of rbtree_postorder_for_each_entry_safe()
.
Thanks, works fine now!
Hmm, did already close this issue but maybe it should remain open util the fix is in master?
The jool's pool4 db flush seem to always crash, looks like use-after-free based on memory poison values in registers. 0x6b = POISON_FREE Added some printk debugs to src/mod/common/db/pool4/db.c
Jool version is 4.1.5 and kernel version is 4.19.181.
Following memory debugging options are enabled in the kernel:
Backtrace from crash