On Fri, Aug 28, 2020 at 5:18 AM <peterz@xxxxxxxxxxxxx> wrote: > So the freelist->refs thing is supposed to pin freelist->next for > concurrent usage, but if we instantly stick it on the > current->kretprobe_instances llist while it's still elevated, we'll > overwrite ->next, which would be bad. I thought about this some more, and actually, it should be safe. The next is not supposed to be changed while the node has non-zero ref-count, true, but this is only important while the node is in the freelist. If it's never added back to the freelist, then there is no problem (the overwritten next may be read but never used). But even if it is later re-added to the freelist, as long as the refcount is still above zero, the node won't actually be in the list right away, and again its next won't matter. When the refcount finally goes down to zero, it will be put on the list but its next will be blindly overwritten at that point. Cameron
