From: Jiang Liu <liuj97@gmail.com>
To: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
sworddragon2@aol.com
Cc: Jiang Liu <jiang.liu@huawei.com>,
bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org
Subject: [PATCH 2/2] mm: protect si_meminfo() and si_meminfo_node() from memory hotplug operations
Date: Sun, 17 Feb 2013 00:27:26 +0800 [thread overview]
Message-ID: <1361032046-1725-2-git-send-email-jiang.liu@huawei.com> (raw)
In-Reply-To: <1361032046-1725-1-git-send-email-jiang.liu@huawei.com>
In-Reply-To: <alpine.DEB.2.02.1302131915170.8584@chino.kir.corp.google.com>
There's typical usage of si_meminfo as below:
si_meminfo(&si);
threshold = si->totalram - si.totalhigh;
It may cause underflow if memory hotplug races with si_meminfo() because
there's no mechanism to protect si_meminfo() from memory hotplug
operations. And some callers expects that si_meminfo() is a lightweight
operations. So introduce a lightweight mechanism to protect si_meminfo()
from memory hotplug operations.
Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
---
mm/page_alloc.c | 24 +++++++++++++++++++++---
1 file changed, 21 insertions(+), 3 deletions(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 6884dc5..5cf03d4 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -2831,18 +2831,34 @@ static inline void show_node(struct zone *zone)
void si_meminfo(struct sysinfo *val)
{
int nid;
- unsigned long present_pages = 0;
+ unsigned long present_pages;
+ val->sharedram = 0;
+ val->mem_unit = PAGE_SIZE;
+
+restart:
+ present_pages = 0;
for_each_node_state(nid, N_MEMORY)
present_pages += node_present_pages(nid);
val->totalram = present_pages;
- val->sharedram = 0;
val->freeram = global_page_state(NR_FREE_PAGES);
val->bufferram = nr_blockdev_pages();
val->totalhigh = totalhigh_pages;
val->freehigh = nr_free_highpages();
- val->mem_unit = PAGE_SIZE;
+
+ /*
+ * si_meminfo() may generate invalid results because it isn't protected
+ * from memory hotplug operaitons. And some callers expect that it's an
+ * lightweigh operation. So provide minimal protections without heavy
+ * overhead.
+ */
+ if (val->totalram < val->freeram ||
+ val->totalram < val->bufferram ||
+ val->totalram < val->totalhigh ||
+ val->totalhigh < val->freehigh ||
+ val->freeram < val->freehigh)
+ goto restart;
}
EXPORT_SYMBOL(si_meminfo);
@@ -2854,6 +2870,7 @@ void si_meminfo_node(struct sysinfo *val, int nid)
unsigned long managed_pages = 0;
pg_data_t *pgdat = NODE_DATA(nid);
+ lock_memory_hotplug();
for (zone_type = 0; zone_type < MAX_NR_ZONES; zone_type++)
managed_pages += pgdat->node_zones[zone_type].managed_pages;
@@ -2874,6 +2891,7 @@ void si_meminfo_node(struct sysinfo *val, int nid)
val->freehigh = 0;
#endif
val->mem_unit = PAGE_SIZE;
+ unlock_memory_hotplug();
}
#endif
--
1.7.9.5
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-16 16:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-53501-27@https.bugzilla.kernel.org/>
2013-02-13 0:51 ` [Bug 53501] New: Duplicated MemTotal with different values Andrew Morton
2013-02-13 1:45 ` David Rientjes
2013-02-13 3:59 ` Andrew Morton
2013-02-14 3:19 ` David Rientjes
2013-02-14 4:01 ` Jiang Liu
2013-02-15 0:26 ` David Rientjes
2013-02-20 5:21 ` Simon Jeons
2013-02-20 7:09 ` David Rientjes
2013-03-02 2:21 ` Simon Jeons
2013-03-04 11:18 ` David Rientjes
2013-03-04 23:39 ` Simon Jeons
2013-03-05 21:53 ` David Rientjes
2013-02-16 16:27 ` [PATCH 1/2] vm: add 'MemManaged' field to /proc/meminfo and /sys/.../nodex/meminfo Jiang Liu
2013-02-19 21:29 ` David Rientjes
2013-02-20 17:27 ` [PATCH v2] mm: let /proc/meminfo report physical memory installed as "MemTotal" Jiang Liu
2013-02-20 22:49 ` Andrew Morton
2013-02-21 17:26 ` Jiang Liu
2013-02-21 21:31 ` Andrew Morton
2013-02-22 19:22 ` Jiang Liu
2013-02-16 16:27 ` Jiang Liu [this message]
2013-02-19 21:32 ` [PATCH 2/2] mm: protect si_meminfo() and si_meminfo_node() from memory hotplug operations David Rientjes
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=1361032046-1725-2-git-send-email-jiang.liu@huawei.com \
--to=liuj97@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jiang.liu@huawei.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sworddragon2@aol.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;
as well as URLs for NNTP newsgroup(s).