From: piliu <piliu@redhat.com>
To: "Thadeu Lima de Souza Cascardo" <cascardo@canonical.com>,
"HAGIO KAZUHITO(萩尾 一仁)" <k-hagio-ab@nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Michal Hocko <mhocko@kernel.org>, Qian Cai <cai@lca.pw>,
Andrew Morton <akpm@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Oscar Salvador <osalvador@suse.de>
Subject: Re: [PATCH] makedumpfile: cope with not-present mem section
Date: Wed, 29 Apr 2020 17:32:11 +0800 [thread overview]
Message-ID: <769ddb8a-c845-04a6-0064-d674bbd04ae3@redhat.com> (raw)
In-Reply-To: <20200128193302.GC4080@calabresa>
Hi Kazu and Cascardo,
I encounter a weird problem when running makedumpfile on a s390 machine.
Our production kernel uses extreme sparse memory model, and has the
following:
in mm/sparse.c
#ifdef CONFIG_SPARSEMEM_EXTREME
struct mem_section **mem_section;
#else
struct mem_section mem_section[NR_SECTION_ROOTS][SECTIONS_PER_ROOT]
____cacheline_internodealigned_in_smp;
#endif
So in makedumpfile.c, get_mem_section(), it got a failed result when the
first call site to validate_mem_section(), then it should success at the
second call site to validate_mem_section(), which is inside if
(is_sparsemem_extreme()) condition.
But the actual result is not like expected.
After introducing
commit e113f1c974c820f9633dc0073eda525d7575f365 [PATCH] cope with
not-present mem section
I got two successful calls to validate_mem_section(), and finally failed
at the condition
ret = symbol_valid ^ pointer_valid;
if (!ret) {
ERRMSG("Could not validate mem_section.\n");
}
Do you have any idea?
Thanks,
Pingfan
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next parent reply other threads:[~2020-04-29 9:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1579487124-28426-1-git-send-email-piliu@redhat.com>
[not found] ` <2AA47CAB-ED13-4A0A-9288-063832158203@redhat.com>
[not found] ` <20200120085919.GB16539@MiWiFi-R3L-srv>
[not found] ` <44958c3d-c861-8eb0-5713-50c36c7cfc6e@redhat.com>
[not found] ` <TY2PR01MB5210FAB04501E6C59AAB2B06DD0F0@TY2PR01MB5210.jpnprd01.prod.outlook.com>
[not found] ` <20200127170447.GA4080@calabresa>
[not found] ` <20200127180627.GB4080@calabresa>
[not found] ` <TY2PR01MB521005B2E72D78C4561C0562DD0A0@TY2PR01MB5210.jpnprd01.prod.outlook.com>
[not found] ` <20200128193302.GC4080@calabresa>
2020-04-29 9:32 ` piliu [this message]
2020-04-29 14:27 ` [PATCH] makedumpfile: cope with not-present mem section HAGIO KAZUHITO(萩尾 一仁)
2020-04-30 8:37 ` piliu
2020-04-30 20:37 ` HAGIO KAZUHITO(萩尾 一仁)
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=769ddb8a-c845-04a6-0064-d674bbd04ae3@redhat.com \
--to=piliu@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=cascardo@canonical.com \
--cc=dan.j.williams@intel.com \
--cc=k-hagio-ab@nec.com \
--cc=kexec@lists.infradead.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.