diff options
author | Dave Hansen <haveblue@us.ibm.com> | 2005-10-29 18:16:52 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-10-29 21:40:44 -0700 |
commit | c6a57e19e464db118dc4ab9cfe9e9748c6d630a0 (patch) | |
tree | 1be192e4c0635c9aa49c8c76d1606e606ecdc9a0 /security/Kconfig | |
parent | 4ca644d970bf2542623228a4624af356d20ca267 (diff) | |
download | op-kernel-dev-c6a57e19e464db118dc4ab9cfe9e9748c6d630a0.zip op-kernel-dev-c6a57e19e464db118dc4ab9cfe9e9748c6d630a0.tar.gz |
[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 <haveblue@us.ibm.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'security/Kconfig')
0 files changed, 0 insertions, 0 deletions