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  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]
Date:   Wed, 13 Feb 2019 13:24:58 +0100
From:   Michal Hocko <mhocko@...nel.org>
To:     Minchan Kim <minchan@...nel.org>
Cc:     gregkh@...uxfoundation.org, linux-mm <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Johannes Weiner <hannes@...xchg.org>,
        "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Hugh Dickins <hughd@...gle.com>,
        Liu Bo <bo.liu@...ux.alibaba.com>, stable@...r.kernel.org
Subject: Re: [PATCH] mm: Fix the pgtable leak

On Wed 13-02-19 21:12:00, Minchan Kim wrote:
> On Wed, Feb 13, 2019 at 01:03:30PM +0100, Michal Hocko wrote:
> > On Wed 13-02-19 20:29:00, Minchan Kim wrote:
> > > [1] was backported to v4.9 stable tree but it introduces pgtable
> > > memory leak because with fault retrial, preallocated pagetable
> > > could be leaked in second iteration.
> > > To fix the problem, this patch backport [2].
> > > 
> > > [1] 5cf3e5ff95876, mm, memcg: fix reclaim deadlock with writeback
> > > [2] b0b9b3df27d10, mm: stop leaking PageTables
> > > 
> > > Fixes: 5cf3e5ff95876 ("mm, memcg: fix reclaim deadlock with writeback")
> > > Cc: Johannes Weiner <hannes@...xchg.org>
> > > Cc: Kirill A. Shutemov <kirill.shutemov@...ux.intel.com>
> > > Cc: Michal Hocko <mhocko@...e.com>
> > > Cc: Andrew Morton <akpm@...ux-foundation.org>
> > > Cc: Hugh Dickins <hughd@...gle.com>
> > > Cc: Liu Bo <bo.liu@...ux.alibaba.com>
> > > Cc: <stable@...r.kernel.org> [4.9]
> > > Signed-off-by: Minchan Kim <minchan@...nel.org>
> > 
> > Thanks for catching this dependency. Do I assume it correctly that this
> > is stable-4.9 only?
> 
> I have no idea how I could find it automatically that a stable patch of
> linus tree is spread out with several stable trees(Hope Greg has an
> answer). I just checked 4.4 longterm kernel and couldn't find it in there.

See http://lkml.kernel.org/r/20190115174036.GA24149@dhcp22.suse.cz

But my question was more about "this is a stable only thing"? It was not
obvious from the subject so I wanted to be sure that I am not missing
anything.
-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists