From: Rusty Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org, frankeh@watson.ibm.com, akpm@zip.com.au
Subject: [PATCH] Futex update III: don't use put_page...
Date: Thu, 06 Jun 2002 17:04:17 +1000 [thread overview]
Message-ID: <E17FrJh-0003jW-00@wagner.rustcorp.com.au> (raw)
I know nothing of VM, but put_page on a page on the LRU list hits a
BUG() inside __free_pages_ok(). Andrew Morton said this was right.
Name: Unpin page bug fix.
Author: Rusty Russell
Status: Tested on 2.5.20
D: This uses page_cache_release() instead of put_page(), as it might
D: be a pagecache page.
diff -urN -I \$.*\$ --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.5.20.1460/kernel/futex.c linux-2.5.20.1460.updated/kernel/futex.c
--- linux-2.5.20.1460/kernel/futex.c Sat May 25 14:35:00 2002
+++ linux-2.5.20.1460.updated/kernel/futex.c Wed Jun 5 21:24:37 2002
@@ -33,6 +33,7 @@
#include <linux/futex.h>
#include <linux/highmem.h>
#include <linux/time.h>
+#include <linux/pagemap.h>
#include <asm/uaccess.h>
/* These mutexes are a very simple counter: the winner is the one who
@@ -69,6 +70,14 @@
return &futex_queues[hash_long(h, FUTEX_HASHBITS)];
}
+static inline void unpin_page(struct page *page)
+{
+ /* Avoid releasing the page which is on the LRU list. I don't
+ know if this is correct, but it stops the BUG() in
+ __free_pages_ok(). */
+ page_cache_release(page);
+}
+
static int futex_wake(struct list_head *head,
struct page *page,
unsigned int offset,
@@ -218,7 +227,7 @@
default:
ret = -EINVAL;
}
- put_page(page);
+ unpin_page(page);
return ret;
}
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
reply other threads:[~2002-06-06 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E17FrJh-0003jW-00@wagner.rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@zip.com.au \
--cc=frankeh@watson.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®