).
Mikhail Zaslonko (1):
mm, memory_hotplug: Initialize struct pages for the full memory
section
mm/page_alloc.c | 12
1 file changed, 12 insertions(+)
--
2.16.4
d+0x5a/0xb0
[<00b86ba0>] system_call+0xdc/0x2d8
Last Breaking-Event-Address:
[<0038596c>] is_mem_section_removable+0xb4/0x190
Kernel panic - not syncing: Fatal exception: panic_on_oops
Fix the problem by initializing the last memory section of each zone
in memmap_i
).
Mikhail Zaslonko (1):
mm, memory_hotplug: Initialize struct pages for the full memory
section
mm/page_alloc.c | 15 +++
1 file changed, 15 insertions(+)
--
2.16.4
;] system_call+0xdc/0x2d8
Last Breaking-Event-Address:
[<00385b26>] test_pages_in_a_zone+0xde/0x160
Kernel panic - not syncing: Fatal exception: panic_on_oops
Fix the problem by initializing the last memory section of the highest zone
in memmap_init_zone() till the very end, even if it goes bey
l fixing specific
functions for memory hotplug sysfs handlers.
Changes v1 -> v2:
* Expanded commit message to show both failing scenarious.
* Use 'pfn + i' instead of 'pfn' for zone_spans_pfn() check within
test_pages_in_a_zone() function thus taking CONFIG_HOLES_IN_ZONE into
co
l fixing specific
functions for memory hotplug sysfs handlers.
Changes v1 -> v2:
* Expanded commit message to show both failing scenarious.
* Use 'pfn + i' instead of 'pfn' for zone_spans_pfn() check within
test_pages_in_a_zone() function thus taking CONFIG_HOLES_IN_ZONE into
co
003b5be2>] ksys_read+0x5a/0xb0
[<00b86ba0>] system_call+0xdc/0x2d8
Last Breaking-Event-Address:
[<0038596c>] is_mem_section_removable+0xb4/0x190
Kernel panic - not syncing: Fatal exception: panic_on_oops
This fix checks if the page lies within the zone boundaries before
acc
003b5be2>] ksys_read+0x5a/0xb0
[<00b86ba0>] system_call+0xdc/0x2d8
Last Breaking-Event-Address:
[<0038596c>] is_mem_section_removable+0xb4/0x190
Kernel panic - not syncing: Fatal exception: panic_on_oops
This fix checks if the page lies within the zone boundaries before
acc
000c001c0>] system_call+0xdc/0x2d8
This fix checks if the page lies within the zone boundaries before
accessing the struct page data. The check is added to both functions.
Actually similar check has already been present in
is_pageblock_removable_nolock() function but only after the struct page
i
000c001c0>] system_call+0xdc/0x2d8
This fix checks if the page lies within the zone boundaries before
accessing the struct page data. The check is added to both functions.
Actually similar check has already been present in
is_pageblock_removable_nolock() function but only after the struct page
i
be uninitialized). But
one reference to nid in show_valid_zones() function has been overlooked.
Fixed with current commit.
Also, nr_pages will not be used any more after test_pages_in_a_zone() call,
do not update it.
Fixes: d0dc12e86b31 ("mm/memory_hotplug: optimize memory hotplug")
Cc: # v4.
be uninitialized). But
one reference to nid in show_valid_zones() function has been overlooked.
Fixed with current commit.
Also, nr_pages will not be used any more after test_pages_in_a_zone() call,
do not update it.
Fixes: d0dc12e86b31 ("mm/memory_hotplug: optimize memory hotplug")
Cc: # v4.
12 matches
Mail list logo