Messages in this thread | | | From | "Alastair D'Silva" <> | Subject | [PATCH v5 0/1] Add bounds check for Hotplugged memory | Date | Mon, 30 Sep 2019 12:21:50 +1000 |
| |
From: Alastair D'Silva <alastair@d-silva.org>
This series adds bounds checks for hotplugged memory, ensuring that it is within the physically addressable range (for platforms that define MAX_(POSSIBLE_)PHYSMEM_BITS.
This allows for early failure, rather than attempting to access bogus section numbers.
Changelog: V5: - Factor out calculation into max_allowed var - Declare unchanging vars as const - Use PFN_PHYS macro instead of shifting by PAGE_SHIFT V4: - Relocate call to __add_pages - Add a warning when the addressable check fails V3: - Perform the addressable check before we take the hotplug lock V2: - Don't use MAX_POSSIBLE_PHYSMEM_BITS as it's wider that what may be available
Alastair D'Silva (1): memory_hotplug: Add a bounds check to __add_pages
mm/memory_hotplug.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
-- 2.21.0
| |