The patch titled
pi-futex: fix mm_struct memory leak
has been added to the -mm tree. Its filename is
pi-futex-fix-mm_struct-memory-leak.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: pi-futex: fix mm_struct memory leak
From: Vernon Mauery <vernux@xxxxxxxxxx>
lock_queue was getting called essentially twice in a row and was
continually incrementing the mm_count ref count, thus causing a memory
leak.
Dinakar Guniguntala provided a proper fix for the problem that simply grabs
the spinlock for the hash bucket queue rather than calling lock_queue.
The second time we do a queue_lock in futex_lock_pi, we really only need to
take the hash bucket lock.
Signed-off-by: Dinakar Guniguntala <dino@xxxxxxxxxx>
Signed-off-by: Vernon Mauery <vernux@xxxxxxxxxx>
Acked-by: Paul E. McKenney <paulmck@xxxxxxxxxx>
Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
kernel/futex.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -puN kernel/futex.c~pi-futex-fix-mm_struct-memory-leak kernel/futex.c
--- a/kernel/futex.c~pi-futex-fix-mm_struct-memory-leak
+++ a/kernel/futex.c
@@ -1208,7 +1208,7 @@ static int do_futex_lock_pi(u32 __user *
}
down_read(&curr->mm->mmap_sem);
- hb = queue_lock(&q, -1, NULL);
+ spin_lock(q.lock_ptr);
/*
* Got the lock. We might not be the anticipated owner if we
_
Patches currently in -mm which might be from vernux@xxxxxxxxxx are
pi-futex-fix-mm_struct-memory-leak.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
