[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected. No action required from the submitter.
The upstream commit SHA1 provided is correct: 2774f256e7c0219e2b0a0894af1c76bdabc4f974
WARNING: Author mismatch between patch and upstream commit: Backport author: jianqi.ren.cn@windriver.com Commit author: Byungchul Parkbyungchul@sk.com
Status in newer kernel trees: 6.14.y | Present (exact SHA1) 6.12.y | Present (exact SHA1) 6.6.y | Present (different SHA1: d6159bd4c005)
Note: The patch differs from the upstream commit: --- 1: 2774f256e7c02 ! 1: dd7506755fcde mm/vmscan: fix a bug calling wakeup_kswapd() with a wrong zone index @@ Metadata ## Commit message ## mm/vmscan: fix a bug calling wakeup_kswapd() with a wrong zone index
+ [ Upstream commit 2774f256e7c0219e2b0a0894af1c76bdabc4f974 ] + With numa balancing on, when a numa system is running where a numa node doesn't have its local memory so it has no managed zones, the following oops has been observed. It's because wakeup_kswapd() is called with a @@ Commit message Cc: Johannes Weiner hannes@cmpxchg.org Cc: stable@vger.kernel.org Signed-off-by: Andrew Morton akpm@linux-foundation.org + Signed-off-by: Jianqi Ren jianqi.ren.cn@windriver.com + Signed-off-by: He Zhe zhe.he@windriver.com
## mm/migrate.c ## -@@ mm/migrate.c: static int numamigrate_isolate_folio(pg_data_t *pgdat, struct folio *folio) +@@ mm/migrate.c: static int numamigrate_isolate_page(pg_data_t *pgdat, struct page *page) if (managed_zone(pgdat->node_zones + z)) break; } @@ mm/migrate.c: static int numamigrate_isolate_folio(pg_data_t *pgdat, struct foli + if (z < 0) + return 0; + - wakeup_kswapd(pgdat->node_zones + z, 0, - folio_order(folio), ZONE_MOVABLE); + wakeup_kswapd(pgdat->node_zones + z, 0, order, ZONE_MOVABLE); return 0; + } ---
Results of testing on various branches:
| Branch | Patch Apply | Build Test | |---------------------------|-------------|------------| | stable/linux-6.1.y | Success | Success |