On 3/24/19 5:38 PM, Sasha Levin wrote:

Hi,

[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag, fixing commit: 6f4576e3687b mempolicy: apply page table walker on queue_pages_range().

The bot has tested the following trees: v5.0.3, v4.19.30, v4.14.107, v4.9.164, v4.4.176.

v5.0.3: Build OK! v4.19.30: Build OK! v4.14.107: Failed to apply! Possible dependencies: Unable to calculate

THP migration is not supported before 4.14, so part of the patch is not applicable, need fix it manually. I'm not quite familiar with the process of stable branch. Should I backport to these versions then send to you?

Thanks, Yang

v4.9.164: Failed to apply! Possible dependencies: 88aaa2a1d732 ("mm: mempolicy: add queue_pages_required()") c8633798497c ("mm: mempolicy: mbind and migrate_pages support thp migration") fd60775aea80 ("mm, thp: avoid unlikely branches for split_huge_pmd")

v4.4.176: Failed to apply! Possible dependencies: 122afea9626a ("mm, vmstats: new THP splitting event") 1c290f642101 ("mm: sanitize page->mapping for tail pages") 248db92da13f ("migrate_pages: try to split pages on queuing") 2a52bcbcc688 ("rmap: extend try_to_unmap() to be usable by split_huge_page()") 6742d293cbe0 ("mm: adjust FOLL_SPLIT for new refcounting") 78ddc5347341 ("thp: rename split_huge_page_pmd() to split_huge_pmd()") 854e9ed09ded ("mm: support madvise(MADV_FREE)") 88aaa2a1d732 ("mm: mempolicy: add queue_pages_required()") ad0bed24e98b ("thp: drop all split_huge_page()-related code") c8633798497c ("mm: mempolicy: mbind and migrate_pages support thp migration") d281ee614518 ("rmap: add argument to charge compound page") eca56ff906bd ("mm, shmem: add internal shmem resident memory accounting") fd60775aea80 ("mm, thp: avoid unlikely branches for split_huge_pmd")

How should we proceed with this patch?

-- Thanks, Sasha