Re: RFC - Winelib constructor init problem

[David Howells]

> No, I don't think it has anything to with exec_domain/personality.

All that this has to do is determine how some signals and syscalls are
handled, but you are probably right.

> What happens if the module goes away?
> The application segfaults I hope.

Depends... if you don't manage it properly then "OOPS"!

Otherwise, it's a matter of making sure that the module _won't_ go away - make
the module register and unregister a handler and its "module definition"
structure (similarly to how the vfs deals with things).

This means:

 (1) A new call can't start if there is no handler registered.

 (2) Whilst a call is in progress, the module's usage counter is kept
     incremented.

 (3) Obviously, the module can't be removed whilst the counter is non-zero.

 (4) There is protection available to make sure you can't tweak a module count
     whilst the module is being loaded/unloaded (so you can't slip in a new
     usage between counter-is-zero-check and actual-removal).

David Howells