From: Michal Hocko <mhocko@kernel.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Regression still in next for drop migrate type checks
Date: Sat, 4 Nov 2017 09:25:00 +0100 [thread overview]
Message-ID: <20171104082500.qvzbb2kw4suo6cgy@dhcp22.suse.cz> (raw)
In-Reply-To: <20171103160012.GF28152@atomide.com>
On Fri 03-11-17 09:00:12, Tony Lindgren wrote:
> Hi all,
>
> Looks like I'm still carrying patch "mm: distinguish CMA and MOVABLE
> isolation in has_unmovable_pages" from Michal [1] for commit e1d753dff0fa
> ("mm: drop migrate type checks from has_unmovable_pages") and Linux next
> has been broken for CMA for few weeks now as noted in the discussion
> also at [1].
>
> What's the status of this regression? How come it's been known
> broken for two weeks and still not fixed or reverted in next?
> This is clearly is not suitable for "wider testing" ;)
This is the first time I hear about the regression. Joonsoo has pointed
out that there might be a problem but he didn't have any specific
failure in hands. The fix has been posted [1] and Andrew has picked it
up few days ago. Could you try to apply that patch? It will show up in
linux-next as soon as Andrew releases mmotm.
[1] http://lkml.kernel.org/r/20171019122118.y6cndierwl2vnguj@dhcp22.suse.cz
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2017-11-04 8:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 16:00 Regression still in next for drop migrate type checks Tony Lindgren
2017-11-03 17:32 ` Andrew Morton
2017-11-03 17:57 ` Tony Lindgren
2017-11-04 8:25 ` Michal Hocko [this message]
2017-11-04 8:35 ` Michal Hocko
2017-11-06 23:22 ` Tony Lindgren
2017-11-06 14:38 ` Tony Lindgren
2017-11-06 14:42 ` Michal Hocko
2017-11-07 2:20 ` Tony Lindgren
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=20171104082500.qvzbb2kw4suo6cgy@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=sfr@canb.auug.org.au \
--cc=tony@atomide.com \
--cc=torvalds@linux-foundation.org \
/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).