The qemu tests currently cache the test image, as well as using cache=unsafe,
and so it's possible for image corruption to happen across tests. Using
the -snapshot qemu option causes qemu to run each test using the base
image file without needing to re-create it, but each test's modifications
are discarded between tests, which should avoid image corruption or
test-to-test failure propagation.
8dd294c...
by
Lennart Poettering <email address hidden>
portabled: add BindPaths=/run back into "trusted" policy
This partly reverts fe239c7d7d6227209234100f4e0a36dd952a5587, where I
accidentally dropped only line for /run that was unlike the others.
Oops.
Let's fix this by making the userdata inheritance from VarlinkServer
object to the Varlink connection object optional: we want it for most
cases, but not all, i.e. all those cases where the calls implemented as
varlink methods are stateless and can be answered synchronously. For the
other cases (i.e. where we want per-connection objects that wrap the
asynchronous operation as it goes on) let's not do such inheritance but
initialize the userdata pointer only once we have it. THis means the
original manager object must be manually retrieved from the
VarlinkServer object, which in turn needs to be requested from the
Varlink connection object.
The userdata inheritance is now controlled by the
VARLINK_INHERIT_USERDATA flag passed at VarlinkServer construction.
