From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BA2EFC43381 for ; Mon, 25 Mar 2019 16:27:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 92FAF2087C for ; Mon, 25 Mar 2019 16:27:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726182AbfCYQ12 (ORCPT ); Mon, 25 Mar 2019 12:27:28 -0400 Received: from out30-131.freemail.mail.aliyun.com ([115.124.30.131]:43764 "EHLO out30-131.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725788AbfCYQ12 (ORCPT ); Mon, 25 Mar 2019 12:27:28 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R101e4;CH=green;DM=||false|;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01f04427;MF=yang.shi@linux.alibaba.com;NM=1;PH=DS;RN=5;SR=0;TI=SMTPD_---0TNdr2s7_1553531240; Received: from US-143344MP.local(mailfrom:yang.shi@linux.alibaba.com fp:SMTPD_---0TNdr2s7_1553531240) by smtp.aliyun-inc.com(127.0.0.1); Tue, 26 Mar 2019 00:27:22 +0800 Subject: Re: [PATCH] mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified To: Sasha Levin , chrubis@suse.cz, vbabka@suse.cz, kirill@shutemov.name Cc: stable@vger.kernel.org References: <1553020556-38583-1-git-send-email-yang.shi@linux.alibaba.com> <20190325003838.E43E12171F@mail.kernel.org> From: Yang Shi Message-ID: <06d1984b-8ff1-57be-63f3-1c03ae60b998@linux.alibaba.com> Date: Mon, 25 Mar 2019 09:27:16 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20190325003838.E43E12171F@mail.kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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