From: Mel Gorman <mgorman@techsingularity.net>
To: James Hogan <james.hogan@imgtec.com>
Cc: linux-metag@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] metag: Drop show_mem() from mem_init()
Date: Fri, 5 Aug 2016 13:32:51 +0100 [thread overview]
Message-ID: <20160805123251.GT2799@techsingularity.net> (raw)
In-Reply-To: <20160805121704.32198-1-james.hogan@imgtec.com>
On Fri, Aug 05, 2016 at 01:17:04PM +0100, James Hogan wrote:
> The recent commit 599d0c954f91 ("mm, vmscan: move LRU lists to node"),
> changed memory management code so that show_mem() is no longer safe to
> call prior to setup_per_cpu_pageset(), as pgdat->per_cpu_nodestats will
> still be NULL. This causes an oops on metag due to the call to
> show_mem() from mem_init():
>
> node_page_state_snapshot(...) + 0x48
> pgdat_reclaimable(struct pglist_data * pgdat = 0x402517a0)
> show_free_areas(unsigned int filter = 0) + 0x2cc
> show_mem(unsigned int filter = 0) + 0x18
> mem_init()
> mm_init()
> start_kernel() + 0x204
>
> This wasn't a problem before with zone_reclaimable() as zone_pcp_init()
> was already setting zone->pageset to &boot_pageset, via setup_arch() and
> paging_init(), which happens before mm_init():
>
> zone_pcp_init(...)
> free_area_init_core(...) + 0x138
> free_area_init_node(int nid = 0, ...) + 0x1a0
> free_area_init_nodes(...) + 0x440
> paging_init(unsigned long mem_end = 0x4fe00000) + 0x378
> setup_arch(char ** cmdline_p = 0x4024e038) + 0x2b8
> start_kernel() + 0x54
>
> No other arches appear to call show_mem() during boot, and it doesn't
> really add much value to the log, so lets just drop it from mem_init().
>
> Signed-off-by: James Hogan <james.hogan@imgtec.com>
> Cc: Mel Gorman <mgorman@techsingularity.net>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
prev parent reply other threads:[~2016-08-05 12:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-05 12:17 [PATCH] metag: Drop show_mem() from mem_init() James Hogan
2016-08-05 12:32 ` Mel Gorman [this message]
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=20160805123251.GT2799@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-metag@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;
as well as URLs for NNTP newsgroup(s).