From: jani@ubuntu.com (Jani Monoses)
To: linux-arm-kernel@lists.infradead.org
Subject: Can switching to FLATMEM cause bugs?
Date: Mon, 10 Jun 2013 09:13:05 +0000 (UTC) [thread overview]
Message-ID: <kp45b0$uue$1@ger.gmane.org> (raw)
Hello,
enabling memory control groups in a Nexus 4 kernel causes boot hangs due
to what I think is a mismatch between where the cgroup code looks for
memory blocks to account for and physical memory layout of the Nexus 4
platform. It skips two blocks which are not aligned to 64K which is the
increment used by memcg initialization code. When later there are
references to pages in one of these blocks, there's a page fault due to
invalid cgroup block links.
I found a workaround to be switching to FLATMEM from SPARSEMEM. Could
this switch cause bugs by itself? I am not sure whether a certain choice
of memory model is only about best resource utilization and performance
or it has implications on the correctness of the memory manager.
thanks
Jani
PS: The details of what I think is the bug on the cgroup mailing list
http://permalink.gmane.org/gmane.linux.kernel.cgroups/7003
reply other threads:[~2013-06-10 9:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='kp45b0$uue$1@ger.gmane.org' \
--to=jani@ubuntu.com \
--cc=linux-arm-kernel@lists.infradead.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).