public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Yang Shi <yang.shi@linux.alibaba.com>
Cc: chrubis@suse.cz, vbabka@suse.cz, kirill@shutemov.name,
	stable@vger.kernel.org
Subject: Re: [PATCH] mm: mempolicy: make mbind() return -EIO when MPOL_MF_STRICT is specified
Date: Tue, 26 Mar 2019 20:25:36 -0400	[thread overview]
Message-ID: <20190327002536.GG25262@sasha-vm> (raw)
In-Reply-To: <06d1984b-8ff1-57be-63f3-1c03ae60b998@linux.alibaba.com>

On Mon, Mar 25, 2019 at 09:27:16AM -0700, Yang Shi wrote:
>
>
>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?

You can send them to stable@vger.kernel.org . Thanks!

--
Thanks,
Sasha

  reply	other threads:[~2019-03-27  0:25 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
2019-03-27  0:25     ` Sasha Levin [this message]
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=20190327002536.GG25262@sasha-vm \
    --to=sashal@kernel.org \
    --cc=chrubis@suse.cz \
    --cc=kirill@shutemov.name \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    --cc=yang.shi@linux.alibaba.com \
    /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