summaryrefslogtreecommitdiff
path: root/debian/patches/libpager_deadlock.patch
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches/libpager_deadlock.patch')
-rw-r--r--debian/patches/libpager_deadlock.patch20
1 files changed, 20 insertions, 0 deletions
diff --git a/debian/patches/libpager_deadlock.patch b/debian/patches/libpager_deadlock.patch
new file mode 100644
index 00000000..ea2d9087
--- /dev/null
+++ b/debian/patches/libpager_deadlock.patch
@@ -0,0 +1,20 @@
+See http://lists.gnu.org/archive/html/bug-hurd/2010-03/msg00127.html
+for the story. This should be completely safe, but Sergio believes
+memory_object_lock_request shouldn't actually block.
+
+diff --git a/libpager/lock-object.c b/libpager/lock-object.c
+index d108666..d8d4a1b 100644
+--- a/libpager/lock-object.c
++++ b/libpager/lock-object.c
+@@ -65,9 +65,11 @@ _pager_lock_object (struct pager *p,
+ }
+ }
+
++ mutex_unlock (&p->interlock);
+ memory_object_lock_request (p->memobjcntl, offset, size, should_return,
+ should_flush, lock_value,
+ sync ? p->port.port_right : MACH_PORT_NULL);
++ mutex_lock (&p->interlock);
+
+ if (sync)
+ {