From: Bharata B Rao <bharata@in.ibm.com>
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: Andi Kleen <ak@suse.de>, Ray Bryant <raybry@mpdtxmail.amd.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64
Date: Wed, 15 Feb 2006 11:16:20 +0530 [thread overview]
Message-ID: <20060215054620.GA2966@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602141131280.14488@schroedinger.engr.sgi.com>
On Tue, Feb 14, 2006 at 11:33:00AM -0800, Christoph Lameter wrote:
> I just took another look at this issue and I cannot see anything wrong. An
> empty zone should be ignored by the page allocator since nr_free == 0. My
> patch should not be needed.
There is a check for list_empty(&area->free_list) in __rmqueue(), which
I think is one of the points in the page allocator where the emptiness of
the free_area list is checked. The current zone(when the crash happens)
bypasses this test leading to this crash.
>
> Could you get us the contents of the struct zone that the page allocator
> is trying to get memory from?
The zone looks like this:
crash> p *(struct zone *)0xffff81000000e700
$1 = {
free_pages = 0,
pages_min = 0,
pages_low = 0,
pages_high = 0,
lowmem_reserve = {0, 0, 0, 0},
pageset = {0xffff81000c013740, 0xffff81013fc42f40, 0xffffffff8071d600,
0xffffffff8071d680, 0xffffffff8071d700, 0xffffffff8071d780,
0xffffffff8071d800, 0xffffffff8071d880, 0xffffffff8071d900,
0xffffffff8071d980, 0xffffffff8071da00, 0xffffffff8071da80,
0xffffffff8071db00, 0xffffffff8071db80, 0xffffffff8071dc00,
0xffffffff8071dc80, 0xffffffff8071dd00, 0xffffffff8071dd80,
0xffffffff8071de00, 0xffffffff8071de80, 0xffffffff8071df00,
0xffffffff8071df80, 0xffffffff8071e000, 0xffffffff8071e080,
0xffffffff8071e100, 0xffffffff8071e180, 0xffffffff8071e200,
0xffffffff8071e280, 0xffffffff8071e300, 0xffffffff8071e380,
0xffffffff8071e400, 0xffffffff8071e480},
lock = {
raw_lock = {
slock = 0
},
break_lock = 1
},
free_area = {{
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}, {
free_list = {
next = 0x0,
prev = 0x0
},
nr_free = 0
}},
_pad1_ = {
x = 0xffff81000000e980 "\001"
},
lru_lock = {
raw_lock = {
slock = 1
},
break_lock = 0
},
active_list = {
next = 0xffff81000000e988,
prev = 0xffff81000000e988
},
inactive_list = {
next = 0xffff81000000e998,
prev = 0xffff81000000e998
},
nr_scan_active = 0,
nr_scan_inactive = 0,
nr_active = 0,
nr_inactive = 0,
pages_scanned = 0,
all_unreclaimable = 0,
reclaim_in_progress = {
counter = 0
},
last_unsuccessful_zone_reclaim = 0,
temp_priority = 12,
prev_priority = 12,
_pad2_ = {
x = 0xffff81000000ea00 ""
},
wait_table = 0x0,
wait_table_size = 0,
wait_table_bits = 0,
zone_pgdat = 0xffff81000000e000,
zone_mem_map = 0x0,
zone_start_pfn = 0,
spanned_pages = 0,
present_pages = 0,
name = 0xffffffff804a858c "Normal"
}
Regards,
Bharata.
next prev parent reply other threads:[~2006-02-15 5:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060205163618.GB21972@in.ibm.com>
2006-02-05 17:03 ` [discuss] mmap, mbind and write to mmap'ed memory crashes 2.6.16-rc1[2] on 2 node X86_64 Andi Kleen
2006-02-06 16:11 ` Christoph Lameter
2006-02-06 18:12 ` Andi Kleen
2006-02-06 18:25 ` Christoph Lameter
2006-02-06 18:31 ` Andi Kleen
2006-02-06 18:45 ` Christoph Lameter
2006-02-06 18:55 ` Andi Kleen
2006-02-06 19:22 ` Christoph Lameter
2006-02-07 5:59 ` Bharata B Rao
2006-02-07 16:49 ` Christoph Lameter
2006-02-07 23:27 ` Ray Bryant
2006-02-07 23:36 ` Andi Kleen
2006-02-08 12:10 ` Bharata B Rao
2006-02-08 15:42 ` Christoph Lameter
2006-02-08 15:45 ` Andi Kleen
2006-02-08 15:59 ` Christoph Lameter
2006-02-08 16:06 ` Andi Kleen
2006-02-08 16:20 ` Christoph Lameter
2006-02-08 16:27 ` Andi Kleen
2006-02-08 16:51 ` Christoph Lameter
2006-02-09 4:39 ` Bharata B Rao
2006-02-09 9:58 ` Andi Kleen
2006-02-14 19:33 ` Christoph Lameter
2006-02-15 5:46 ` Bharata B Rao [this message]
2006-02-15 10:38 ` Bharata B Rao
2006-02-15 11:21 ` Andi Kleen
2006-02-15 18:14 ` Christoph Lameter
2006-02-16 5:18 ` Bharata B Rao
2006-02-15 18:10 ` Christoph Lameter
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=20060215054620.GA2966@in.ibm.com \
--to=bharata@in.ibm.com \
--cc=ak@suse.de \
--cc=clameter@engr.sgi.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raybry@mpdtxmail.amd.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