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.patch22
1 files changed, 0 insertions, 22 deletions
diff --git a/debian/patches/libpager_deadlock.patch b/debian/patches/libpager_deadlock.patch
deleted file mode 100644
index b9bc4e18..00000000
--- a/debian/patches/libpager_deadlock.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-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.
-
-merged upstream
-
-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)
- {