linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Linux Memory Management <linux-mm@kvack.org>,
	Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Nick Piggin <npiggin@suse.de>
Subject: [patch 2/3] mm: locks_freed fix
Date: Sat,  7 Oct 2006 15:05:54 +0200 (CEST)	[thread overview]
Message-ID: <20061007105815.14024.99053.sendpatchset@linux.site> (raw)
In-Reply-To: <20061007105758.14024.70048.sendpatchset@linux.site>

Move the lock debug checks below the page reserved checks.
Also, having debug_check_no_locks_freed in kernel_map_pages is wrong.

Signed-off-by: Nick Piggin <npiggin@suse.de>

Index: linux-2.6/include/linux/mm.h
===================================================================
--- linux-2.6.orig/include/linux/mm.h	2006-10-06 11:59:47.000000000 +1000
+++ linux-2.6/include/linux/mm.h	2006-10-06 12:00:02.000000000 +1000
@@ -1038,12 +1038,7 @@ static inline void vm_stat_account(struc
 
 #ifndef CONFIG_DEBUG_PAGEALLOC
 static inline void
-kernel_map_pages(struct page *page, int numpages, int enable)
-{
-	if (!PageHighMem(page) && !enable)
-		debug_check_no_locks_freed(page_address(page),
-					   numpages * PAGE_SIZE);
-}
+kernel_map_pages(struct page *page, int numpages, int enable) {}
 #endif
 
 extern struct vm_area_struct *get_gate_vma(struct task_struct *tsk);
Index: linux-2.6/mm/page_alloc.c
===================================================================
--- linux-2.6.orig/mm/page_alloc.c	2006-10-06 11:59:47.000000000 +1000
+++ linux-2.6/mm/page_alloc.c	2006-10-06 12:01:52.000000000 +1000
@@ -443,15 +443,13 @@ static void __free_pages_ok(struct page 
 	int i;
 	int reserved = 0;
 
-	if (!PageHighMem(page))
-		debug_check_no_locks_freed(page_address(page),
-					   PAGE_SIZE<<order);
-
 	for (i = 0 ; i < (1 << order) ; ++i)
 		reserved += free_pages_check(page + i);
 	if (reserved)
 		return;
 
+	if (!PageHighMem(page))
+		debug_check_no_locks_freed(page_address(page),PAGE_SIZE<<order);
 	arch_free_page(page, order);
 	kernel_map_pages(page, 1 << order, 0);
 
@@ -723,6 +721,8 @@ static void fastcall free_hot_cold_page(
 	if (free_pages_check(page))
 		return;
 
+	if (!PageHighMem(page))
+		debug_check_no_locks_freed(page_address(page), PAGE_SIZE);
 	arch_free_page(page, 0);
 	kernel_map_pages(page, 1, 0);
 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2006-10-07 13:05 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 13:05 [rfc] 2.6.19-rc1: vm stuff Nick Piggin
2006-10-07 13:05 ` [patch 1/3] mm: arch_free_page fix Nick Piggin
2006-10-07 13:05 ` Nick Piggin [this message]
2006-10-07 13:06 ` [patch 3/3] mm: add arch_alloc_page Nick Piggin
2006-10-07 20:43   ` Andrew Morton
2006-10-08  1:39     ` Nick Piggin
2006-10-11 14:48       ` Martin Schwidefsky
2006-10-11 14:56         ` Nick Piggin
2006-10-11 15:07           ` Martin Schwidefsky
2006-10-07 13:06 ` [patch 1/3] mm: fault vs invalidate/truncate check Nick Piggin
2006-10-07 13:06 ` [patch 2/3] mm: fault vs invalidate/truncate race fix Nick Piggin
2006-10-07 20:43   ` Andrew Morton
2006-10-07 20:44   ` Andrew Morton
2006-10-08  2:05     ` Nick Piggin
2006-10-07 13:06 ` [patch 3/3] mm: fault handler to replace nopage and populate Nick Piggin
2006-10-07 15:14   ` Jeff Garzik
2006-10-08  2:17     ` Nick Piggin
2006-10-07 20:44   ` Andrew Morton
2006-10-08  2:12     ` Nick Piggin
2006-10-08 23:46     ` Benjamin Herrenschmidt
2006-10-09 10:26       ` Nick Piggin
2006-10-09 10:50         ` Benjamin Herrenschmidt
2006-10-09 11:00           ` Nick Piggin
2006-10-09 11:10             ` Benjamin Herrenschmidt
2006-10-09 11:19               ` Nick Piggin
2006-10-09 11:32                 ` Benjamin Herrenschmidt
2006-10-09 11:45                   ` Nick Piggin
2006-10-09 11:49                     ` Benjamin Herrenschmidt
2006-10-09 11:58                       ` Nick Piggin
2006-10-09 12:07                         ` Benjamin Herrenschmidt
2006-10-09 12:14                           ` Nick Piggin
2006-10-09 13:38                             ` Thomas Hellstrom
2006-10-09 13:52                               ` Nick Piggin
2006-10-09 20:50                                 ` Benjamin Herrenschmidt
2006-10-10  6:11                                   ` Thomas Hellström
2006-10-10  7:55                                     ` Benjamin Herrenschmidt
2006-10-10  8:39                                       ` Thomas Hellstrom
2006-10-09 20:45                               ` Benjamin Herrenschmidt
2006-10-09 12:09                         ` Nick Piggin
2006-10-09 12:11                           ` Benjamin Herrenschmidt
2006-10-10 12:10   ` Christoph Hellwig
2006-10-10 12:13     ` Nick Piggin
2006-10-10 17:52       ` Andrew Morton
2006-10-11  0:43         ` SPAM: " Nick Piggin
     [not found]   ` <5c77e7070610120456t1bdaa95cre611080c9c953582@mail.gmail.com>
2006-10-12 12:07     ` Nick Piggin
2006-10-14 13:28       ` Ingo Oeser
2006-10-15  7:54         ` Nick Piggin
2006-10-24 21:31   ` Dave Airlie
2006-10-26 11:09     ` Nick Piggin

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=20061007105815.14024.99053.sendpatchset@linux.site \
    --to=npiggin@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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