Re: [PATCH] mm: Fix the pgtable leak

2019-02-18 Thread Greg KH
On Wed, Feb 13, 2019 at 08:29:00PM +0900, 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] 5cf3e5ff958

Re: [PATCH] mm: Fix the pgtable leak

2019-02-18 Thread Greg KH
On Mon, Feb 18, 2019 at 05:20:26PM +0900, Minchan Kim wrote: > On Thu, Feb 14, 2019 at 04:23:52PM +0900, Minchan Kim wrote: > > On Wed, Feb 13, 2019 at 02:36:24PM +0100, Greg KH wrote: > > > On Wed, Feb 13, 2019 at 08:29:00PM +0900, Minchan Kim wrote: > > > > [1] was backported to v4.9 stable tree

Re: [PATCH] mm: Fix the pgtable leak

2019-02-18 Thread Minchan Kim
On Thu, Feb 14, 2019 at 04:23:52PM +0900, Minchan Kim wrote: > On Wed, Feb 13, 2019 at 02:36:24PM +0100, Greg KH wrote: > > On Wed, Feb 13, 2019 at 08:29:00PM +0900, Minchan Kim wrote: > > > [1] was backported to v4.9 stable tree but it introduces pgtable > > > memory leak because with fault retria

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Minchan Kim
On Wed, Feb 13, 2019 at 01:24:58PM +0100, Michal Hocko wrote: > 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

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Minchan Kim
On Wed, Feb 13, 2019 at 02:36:24PM +0100, Greg KH wrote: > On Wed, Feb 13, 2019 at 08:29:00PM +0900, 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. >

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Greg KH
On Wed, Feb 13, 2019 at 08:29:00PM +0900, 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] 5cf3e5ff958

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Michal Hocko
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 >

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Minchan Kim
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 th

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Michal Hocko
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: f

Re: [PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Minchan Kim
On Wed, Feb 13, 2019 at 08:29:00PM +0900, 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] 5cf3e5ff958

[PATCH] mm: Fix the pgtable leak

2019-02-13 Thread Minchan Kim
[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: