aboutsummaryrefslogtreecommitdiffstats
path: root/mm/sparse.c
diff options
context:
space:
mode:
authorDave Hansen <[email protected]>2005-10-30 01:16:52 +0000
committerLinus Torvalds <[email protected]>2005-10-30 04:40:44 +0000
commitc6a57e19e464db118dc4ab9cfe9e9748c6d630a0 (patch)
tree1be192e4c0635c9aa49c8c76d1606e606ecdc9a0 /mm/sparse.c
parent[PATCH] memory hotplug prep: __section_nr helper (diff)
downloadkernel-c6a57e19e464db118dc4ab9cfe9e9748c6d630a0.tar.gz
kernel-c6a57e19e464db118dc4ab9cfe9e9748c6d630a0.zip
[PATCH] memory hotplug prep: fixup bad_range()
When doing memory hotplug operations, the size of existing zones can obviously change. This means that zone->zone_{start_pfn,spanned_pages} can change. There are currently no locks that protect these structure members. However, they are rarely accessed at runtime. Outside of swsusp, the only place that I can find is bad_range(). So, split bad_range() up into two pieces: one that needs to be locked and anther that doesn't. Signed-off-by: Dave Hansen <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'mm/sparse.c')
0 files changed, 0 insertions, 0 deletions