Fix use-after-free in the lua object management #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Wlroots does not call
wl_list_remove(&destroy.listener_list)
after the destroy signal fires. It is the responsibility of the subscriber to handle their own wl_listener being left with an invalid link.This was an issue because it might happen that the kiwmi_object is not destroyed immediately, but only later by a lua gc handler that finally decrements the refcount to zero. We have to ensure that
kiwmi_object_destroy
can succeed.Here we first use
wl_list_remove
to unsubscribe from the signal, and thenwl_list_init
to leave the link in a valid state forkiwmi_object_destroy
.