On Sat Jan 24, 2026 at 6:05 PM CET, Johan Hovold wrote: > this does not look like the right interface for the chardev unplug issue.
I think it depends, we should do everything to prevent having the issue in the first place, e.g. ensure that we synchronize the unplug properly on device driver unbind. Sometimes, however, this isn't possible; this is where a revocable mechanism can come in handy to prevent UAF of device resources -- DRM is a good example for this. But to be fair, I also want to point out that there is a quite significant difference regarding the usefulness of the revocable concept in C compared to in Rust due to language capabilities.
