On Mon, Jul 21, 2025 at 05:49:02PM +0200, Gabriele Monaco wrote: > Yeah I get your point. If I understand you correctly, what's broken is > that we just return EBUSY and ignore that on __exit instead of doing > something about it (set nop to all monitors using this reactor).
Yeah, EBUSY is ignored. > I wonder if we shouldn't also fix this (using the module refcount). > But that can be done in the future, I'm not even sure reactors as > modules currently work. Yes, let's worry about it when we allow building reactors as modules. > Also, I'd need to verify this but depending on the order of exit > functions, we might be seeing the same problems with built-in reactors > when active on shutdown. I'm going to play a bit with this and see if > this workaround of not deleting the reactor was introduced for that (I > doubt though). I'm not sure I follow. exit functions are never called for built-in reactors. They are even discarded out of the built image. Nam
