search for: nbdkit_get_error

...andles errors is that the thread-local value takes priority and errno is only a fallback if the thread-local value was not set. So, we can either mandate that filters that want to do non-trivial work after calling into next_ops must check what the plugin set (hoist the connections.c:get_error into nbdkit_get_error), and then MUST call nbdkit_set_error to change the error (meaning that filters should not rely on errno for setting the value) - or we can change the semantics of the backend and filters to say that instead of returning -1, we return the actual error code. Plugins still return -1 for backward com...

On Wed, Jan 31, 2018 at 09:26:37PM -0600, Eric Blake wrote: > Previously, we let a plugin set an error in either thread-local > storage (nbdkit_set_error()) or errno, then connections.c would > decode which error to use. But with filters in the mix, it is > very difficult for a filter to know what error was set by the > plugin (particularly since nbdkit_set_error() has no public