stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <yang.shi@linux.alibaba.com>
To: Sasha Levin <sashal@kernel.org>,
	chrubis@suse.cz, vbabka@suse.cz, kirill@shutemov.name
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified
Date: Mon, 25 Mar 2019 09:27:16 -0700	[thread overview]
Message-ID: <06d1984b-8ff1-57be-63f3-1c03ae60b998@linux.alibaba.com> (raw)
In-Reply-To: <20190325003838.E43E12171F@mail.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


  parent reply	other threads:[~2019-03-25 16:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 18:35 [PATCH] mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified Yang Shi
2019-03-20  0:49 ` David Rientjes
2019-03-20  1:06   ` Yang Shi
2019-03-20  5:53 ` Souptick Joarder
2019-03-20 22:16   ` Andrew Morton
2019-03-20 23:06     ` Yang Shi
2019-03-20  8:16 ` Oscar Salvador
2019-03-20 18:31   ` Yang Shi
2019-03-20 18:48     ` Oscar Salvador
2019-03-20 15:44 ` Rafael Aquini
     [not found] ` <20190325003838.E43E12171F@mail.kernel.org>
2019-03-25 16:27   ` Yang Shi [this message]
2019-03-27  0:25     ` Sasha Levin
2019-03-31 14:57     ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06d1984b-8ff1-57be-63f3-1c03ae60b998@linux.alibaba.com \
    --to=yang.shi@linux.alibaba.com \
    --cc=chrubis@suse.cz \
    --cc=kirill@shutemov.name \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).