lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171106144216.g6ee3vrzyu7bstzh@dhcp22.suse.cz>
Date:   Mon, 6 Nov 2017 15:42:16 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Tony Lindgren <tony@...mide.com>
Cc:     Joonsoo Kim <iamjoonsoo.kim@....com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Russell King - ARM Linux <linux@...linux.org.uk>,
        linux-kernel@...r.kernel.org
Subject: Re: Regression still in next for drop migrate type checks

On Mon 06-11-17 06:38:04, Tony Lindgren wrote:
> * Michal Hocko <mhocko@...nel.org> [171104 08:26]:
> > 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.
> 
> Yes thanks I can confirm that next-20171106 works for me. So as far as
> I'm concerned, we're good to go.

Can I assume your Tested-by?
-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ