This is only required to avoid a lock inversion between the repo lock
and database table locks, but we have no explicit database table locks
any more.

We do not want to hold the repo lock for an extended period,
particularly when we are running a database retry loop.

In practice, currently, cs-bisection-step always fails with a database
serialisation error.

Signed-off-by: Ian Jackson <ian.jack...@eu.citrix.com>
---
 cs-bisection-step | 1 -
 1 file changed, 1 deletion(-)

diff --git a/cs-bisection-step b/cs-bisection-step
index a0595b2..4c71587 100755
--- a/cs-bisection-step
+++ b/cs-bisection-step
@@ -1405,7 +1405,6 @@ sub compute_exitstatus () {
 }
 
 csreadconfig();
-grabrepolock_reexec(@org_argv);
 reportcmdline();
 findbasics();
 digraph_whole();
-- 
2.1.4


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

Reply via email to