From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] - SPARSEMEM - Change pfn to unsigned long
Date: Wed, 01 Jun 2005 16:41:03 +0000 [thread overview]
Message-ID: <20050601164102.GA15563@sgi.com> (raw)
The latest 2.6.12-rc5-mm2 will not boot on large SGI systems. "pfn"
was assigned to an "int". Large systems overflow an int.
Trivial fix & it works ok now.....
Signed-off-by: Jack Steiner <steiner@sgi.com>
Index: linux/mm/page_alloc.c
=================================--- linux.orig/mm/page_alloc.c 2005-05-26 10:32:26.804141634 -0500
+++ linux/mm/page_alloc.c 2005-06-01 11:28:43.338491345 -0500
@@ -1731,8 +1731,8 @@ void __init memmap_init_zone(unsigned lo
unsigned long start_pfn)
{
struct page *page;
- int end_pfn = start_pfn + size;
- int pfn;
+ unsigned long end_pfn = start_pfn + size;
+ unsigned long pfn;
for (pfn = start_pfn; pfn < end_pfn; pfn++, page++) {
if (!early_pfn_valid(pfn))
Index: linux/mm/sparse.c
=================================--- linux.orig/mm/sparse.c 2005-05-26 10:32:26.816836797 -0500
+++ linux/mm/sparse.c 2005-06-01 10:29:24.435883417 -0500
@@ -124,7 +124,7 @@ void sparse_init(void)
* set. If this is <=0, then that means that the passed-in
* map was not consumed and must be freed.
*/
-int sparse_add_one_section(int start_pfn, int nr_pages, struct page *map)
+int sparse_add_one_section(unsigned long start_pfn, int nr_pages, struct page *map)
{
struct mem_section *ms = __pfn_to_section(start_pfn);
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next reply other threads:[~2005-06-01 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 16:41 Jack Steiner [this message]
2005-06-03 14:53 ` [PATCH] - SPARSEMEM - Change pfn to unsigned long Andy Whitcroft
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=20050601164102.GA15563@sgi.com \
--to=steiner@sgi.com \
--cc=linux-ia64@vger.kernel.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