Re: [PATCH] mm: sections are not offlined during memory hotremove

2018-04-27 Thread Greg KH
On Thu, Apr 26, 2018 at 04:30:02PM -0400, Pavel Tatashin wrote: > Memory hotplug, and hotremove operate with per-block granularity. If > machine has large amount of memory (more than 64G), the size of memory > block can span multiple sections. By mistake, during hotremove we set > only the first se

[PATCH] mm: sections are not offlined during memory hotremove

2018-04-26 Thread Pavel Tatashin
Memory hotplug, and hotremove operate with per-block granularity. If machine has large amount of memory (more than 64G), the size of memory block can span multiple sections. By mistake, during hotremove we set only the first section to offline state. The bug was discovered because kernel selftest

Re: [PATCH] mm: sections are not offlined during memory hotremove

2018-04-26 Thread Michal Hocko
On Thu 26-04-18 21:11:11, Michal Hocko wrote: > On Thu 26-04-18 11:58:34, Pavel Tatashin wrote: > > Memory hotplug, and hotremove operate with per-block granularity. If > > machine has large amount of memory (more than 64G), the size of memory > > block can span multiple sections. By mistake, durin

Re: [PATCH] mm: sections are not offlined during memory hotremove

2018-04-26 Thread Michal Hocko
On Thu 26-04-18 11:58:34, Pavel Tatashin wrote: > Memory hotplug, and hotremove operate with per-block granularity. If > machine has large amount of memory (more than 64G), the size of memory > block can span multiple sections. By mistake, during hotremove we set > only the first section to offline

[PATCH] mm: sections are not offlined during memory hotremove

2018-04-26 Thread Pavel Tatashin
Memory hotplug, and hotremove operate with per-block granularity. If machine has large amount of memory (more than 64G), the size of memory block can span multiple sections. By mistake, during hotremove we set only the first section to offline state. The bug was discovered because kernel selftest