public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Frank <mhf@linuxmail.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: axboe@suse.de, "Randy.Dunlap" <rddunlap@osdl.org>,
	riel@redhat.com, linux-kernel@vger.kernel.org
Subject: [PATCH] 2.4.25-rc1: Shutdown kernel on zone-alignment failure
Date: Sat, 7 Feb 2004 05:34:46 +0800	[thread overview]
Message-ID: <200402070534.46123.mhf@linuxmail.org> (raw)

Marcelo,

The following is applicable to all architectures using zones.

When zone alignment goes wrong, a message is printed:
	BUG: wrong zone alignment, it will crash 

_BUT_ kernel runs until it dies of the alignment problems - it took me 
hours until I found the message after looking elsewhere ;)

This patch: 

- Should zone alignment fail, it will force a BUG() once the BUG handler inits

- Improves the messages of zone init to help debug zone alignment problems

Please apply.

The highmem autoalignment patch will follow after more testing.

Regards
Michael


diff -uN -r -X /home/mhf/sys/dont/dontdiff linux-2.4.25-rc1-Vanilla/include/linux/kernel.h linux-2.4.25-rc1-mhf176/include/linux/kernel.h
--- linux-2.4.25-rc1-Vanilla/include/linux/kernel.h	2004-02-06 17:09:26.000000000 +0800
+++ linux-2.4.25-rc1-mhf176/include/linux/kernel.h	2004-02-07 04:43:49.000000000 +0800
@@ -45,7 +45,7 @@
 #define minimum_console_loglevel (console_printk[2])
 #define default_console_loglevel (console_printk[3])
 
-# define NORET_TYPE    /**/
+# define NORET_TYPE   
 # define ATTRIB_NORET  __attribute__((noreturn))
 # define NORET_AND     noreturn,
 
@@ -104,7 +104,7 @@
 
 extern void bust_spinlocks(int yes);
 extern int oops_in_progress;		/* If set, an oops, panic(), BUG() or die() is in progress */
-
+extern int force_bug;           /* If set, BUG() will be forced when handler initialized */
 extern int tainted;
 extern const char *print_tainted(void);
 
diff -uN -r -X /home/mhf/sys/dont/dontdiff linux-2.4.25-rc1-Vanilla/init/main.c linux-2.4.25-rc1-mhf176/init/main.c
--- linux-2.4.25-rc1-Vanilla/init/main.c	2004-02-06 17:06:58.000000000 +0800
+++ linux-2.4.25-rc1-mhf176/init/main.c	2004-02-07 05:11:07.000000000 +0800
@@ -121,6 +121,7 @@
 extern void time_init(void);
 extern void softirq_init(void);
 
+int force_bug;
 int rows, cols;
 
 char *execute_command;
@@ -422,6 +423,14 @@
 	ccwcache_init();
 #endif
 	signals_init();
+
+	/*
+	 * Something went badly wrong during the early initialisation process,
+	 * so lets die before doing any damage or wasting people's time 
+	 * running a half dead kernel.
+	 */
+	if (force_bug)
+		BUG();
 #ifdef CONFIG_PROC_FS
 	proc_root_init();
 #endif
diff -uN -r -X /home/mhf/sys/dont/dontdiff linux-2.4.25-rc1-Vanilla/mm/page_alloc.c linux-2.4.25-rc1-mhf176/mm/page_alloc.c
--- linux-2.4.25-rc1-Vanilla/mm/page_alloc.c	2004-02-06 17:06:58.000000000 +0800
+++ linux-2.4.25-rc1-mhf176/mm/page_alloc.c	2004-02-07 04:48:30.000000000 +0800
@@ -726,8 +726,8 @@
 	unsigned long i, j;
 	unsigned long map_size;
 	unsigned long totalpages, offset, realtotalpages;
-	const unsigned long zone_required_alignment = 1UL << (MAX_ORDER-1);
-
+	const unsigned long zone_required_alignment = 1UL << (PAGE_SHIFT + MAX_ORDER-1);
+        unsigned long zone_bad_alignment;
 	if (zone_start_paddr & ~PAGE_MASK)
 		BUG();
 
@@ -741,7 +741,8 @@
 		for (i = 0; i < MAX_NR_ZONES; i++)
 			realtotalpages -= zholes_size[i];
 			
-	printk("On node %d totalpages: %lu\n", nid, realtotalpages);
+	printk("On node %d totalpages: %lu, zones aligned at 0x%lx\n",
+	       nid, realtotalpages,zone_required_alignment);
 
 	/*
 	 * Some architectures (with lots of mem and discontinous memory
@@ -774,7 +775,20 @@
 		if (zholes_size)
 			realsize -= zholes_size[j];
 
-		printk("zone(%lu): %lu pages.\n", j, size);
+		printk("zone(%lu): %lu pages, physical start address at 0x%lx\n",
+		       j, size,zone_start_paddr);
+
+		/*
+		 * Here the alignment of a zone is checked. Should alignment
+		 * be wrong, all that can be done is to print an error message
+                 * and defer the the BUG handler as it is not yet initialized.
+		 */
+		if ((zone_bad_alignment = (zone_start_paddr & (zone_required_alignment-1)))) {
+			printk("zone(%lu): FATAL ERROR: wrong zone alignment 0x%lx"
+			       " - will force kernel BUG\n",
+			       j,zone_bad_alignment);
+			force_bug = 1;
+		}
 		zone->size = size;
 		zone->realsize = realsize;
 		zone->name = zone_names[j];
@@ -784,7 +798,6 @@
 		zone->need_balance = 0;
 		 zone->nr_active_pages = zone->nr_inactive_pages = 0;
 
-
 		if (!size)
 			continue;
 
@@ -837,8 +850,6 @@
 		zone->zone_start_mapnr = offset;
 		zone->zone_start_paddr = zone_start_paddr;
 
-		if ((zone_start_paddr >> PAGE_SHIFT) & (zone_required_alignment-1))
-			printk("BUG: wrong zone alignment, it will crash\n");
 
 		/*
 		 * Initially all pages are reserved - free ones are freed


             reply	other threads:[~2004-02-06 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 21:34 Michael Frank [this message]
2004-02-06 21:48 ` [PATCH] 2.4.25-rc1: Shutdown kernel on zone-alignment failure Michael Frank
2004-02-06 22:39 ` Michael Frank

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=200402070534.46123.mhf@linuxmail.org \
    --to=mhf@linuxmail.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=rddunlap@osdl.org \
    --cc=riel@redhat.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