On 1/24/19 6:17 AM, Michal Hocko wrote: > and nr_cpus set to 4. The underlying reason is tha the device is bound > to node 2 which doesn't have any memory and init_cpu_to_node only > initializes memory-less nodes for possible cpus which nr_cpus restrics. > This in turn means that proper zonelists are not allocated and the page > allocator blows up. This looks OK to me. Could we add a few DEBUG_VM checks that *look* for these invalid zonelists? Or, would our existing list debugging have caught this? Basically, is this bug also a sign that we need better debugging around this?
