linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] mm: Fix the pgtable leak
@ 2019-02-13 11:29 Minchan Kim
  2019-02-13 11:33 ` Minchan Kim
                   ` (3 more replies)
  0 siblings, 4 replies; 11+ messages in thread
From: Minchan Kim @ 2019-02-13 11:29 UTC (permalink / raw)
  To: gregkh
  Cc: linux-mm, LKML, Minchan Kim, Johannes Weiner,
	Kirill A . Shutemov, Michal Hocko, Andrew Morton, Hugh Dickins,
	Liu Bo, stable

[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@cmpxchg.org>
Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hughd@google.com>
Cc: Liu Bo <bo.liu@linux.alibaba.com>
Cc: <stable@vger.kernel.org> [4.9]
Signed-off-by: Minchan Kim <minchan@kernel.org>
---
 mm/memory.c | 21 +++++++++++++++------
 1 file changed, 15 insertions(+), 6 deletions(-)

diff --git a/mm/memory.c b/mm/memory.c
index 35d8217bb0467..47248dc0b9e1a 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3329,15 +3329,24 @@ static int do_fault(struct fault_env *fe)
 {
 	struct vm_area_struct *vma = fe->vma;
 	pgoff_t pgoff = linear_page_index(vma, fe->address);
+	int ret;
 
 	/* The VMA was not fully populated on mmap() or missing VM_DONTEXPAND */
 	if (!vma->vm_ops->fault)
-		return VM_FAULT_SIGBUS;
-	if (!(fe->flags & FAULT_FLAG_WRITE))
-		return do_read_fault(fe, pgoff);
-	if (!(vma->vm_flags & VM_SHARED))
-		return do_cow_fault(fe, pgoff);
-	return do_shared_fault(fe, pgoff);
+		ret = VM_FAULT_SIGBUS;
+	else if (!(fe->flags & FAULT_FLAG_WRITE))
+		ret = do_read_fault(fe, pgoff);
+	else if (!(vma->vm_flags & VM_SHARED))
+		ret = do_cow_fault(fe, pgoff);
+	else
+		ret = do_shared_fault(fe, pgoff);
+
+	/* preallocated pagetable is unused: free it */
+	if (fe->prealloc_pte) {
+		pte_free(vma->vm_mm, fe->prealloc_pte);
+		fe->prealloc_pte = 0;
+	}
+	return ret;
 }
 
 static int numa_migrate_prep(struct page *page, struct vm_area_struct *vma,
-- 
2.20.1.791.gb4d0f1c61a-goog


^ permalink raw reply related	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 11:29 [PATCH] mm: Fix the pgtable leak Minchan Kim
@ 2019-02-13 11:33 ` Minchan Kim
  2019-02-13 12:03 ` Michal Hocko
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 11+ messages in thread
From: Minchan Kim @ 2019-02-13 11:33 UTC (permalink / raw)
  To: gregkh
  Cc: linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Michal Hocko, Andrew Morton, Hugh Dickins, Liu Bo, stable,
	Martin Liu

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] 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@cmpxchg.org>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Liu Bo <bo.liu@linux.alibaba.com>
> Cc: <stable@vger.kernel.org> [4.9]
> Signed-off-by: Minchan Kim <minchan@kernel.org>
Reported-by: Martin Liu <liumartin@google.com>


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 11:29 [PATCH] mm: Fix the pgtable leak Minchan Kim
  2019-02-13 11:33 ` Minchan Kim
@ 2019-02-13 12:03 ` Michal Hocko
  2019-02-13 12:12   ` Minchan Kim
  2019-02-13 13:36 ` Greg KH
  2019-02-18 13:33 ` Greg KH
  3 siblings, 1 reply; 11+ messages in thread
From: Michal Hocko @ 2019-02-13 12:03 UTC (permalink / raw)
  To: Minchan Kim
  Cc: gregkh, linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Andrew Morton, Hugh Dickins, Liu Bo, stable

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@cmpxchg.org>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Liu Bo <bo.liu@linux.alibaba.com>
> Cc: <stable@vger.kernel.org> [4.9]
> Signed-off-by: Minchan Kim <minchan@kernel.org>

Thanks for catching this dependency. Do I assume it correctly that this
is stable-4.9 only?

> ---
>  mm/memory.c | 21 +++++++++++++++------
>  1 file changed, 15 insertions(+), 6 deletions(-)
> 
> diff --git a/mm/memory.c b/mm/memory.c
> index 35d8217bb0467..47248dc0b9e1a 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -3329,15 +3329,24 @@ static int do_fault(struct fault_env *fe)
>  {
>  	struct vm_area_struct *vma = fe->vma;
>  	pgoff_t pgoff = linear_page_index(vma, fe->address);
> +	int ret;
>  
>  	/* The VMA was not fully populated on mmap() or missing VM_DONTEXPAND */
>  	if (!vma->vm_ops->fault)
> -		return VM_FAULT_SIGBUS;
> -	if (!(fe->flags & FAULT_FLAG_WRITE))
> -		return do_read_fault(fe, pgoff);
> -	if (!(vma->vm_flags & VM_SHARED))
> -		return do_cow_fault(fe, pgoff);
> -	return do_shared_fault(fe, pgoff);
> +		ret = VM_FAULT_SIGBUS;
> +	else if (!(fe->flags & FAULT_FLAG_WRITE))
> +		ret = do_read_fault(fe, pgoff);
> +	else if (!(vma->vm_flags & VM_SHARED))
> +		ret = do_cow_fault(fe, pgoff);
> +	else
> +		ret = do_shared_fault(fe, pgoff);
> +
> +	/* preallocated pagetable is unused: free it */
> +	if (fe->prealloc_pte) {
> +		pte_free(vma->vm_mm, fe->prealloc_pte);
> +		fe->prealloc_pte = 0;
> +	}
> +	return ret;
>  }
>  
>  static int numa_migrate_prep(struct page *page, struct vm_area_struct *vma,
> -- 
> 2.20.1.791.gb4d0f1c61a-goog
> 

-- 
Michal Hocko
SUSE Labs

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 12:03 ` Michal Hocko
@ 2019-02-13 12:12   ` Minchan Kim
  2019-02-13 12:24     ` Michal Hocko
  0 siblings, 1 reply; 11+ messages in thread
From: Minchan Kim @ 2019-02-13 12:12 UTC (permalink / raw)
  To: Michal Hocko
  Cc: gregkh, linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Andrew Morton, Hugh Dickins, Liu Bo, stable

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@cmpxchg.org>
> > Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > Cc: Michal Hocko <mhocko@suse.com>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Cc: Hugh Dickins <hughd@google.com>
> > Cc: Liu Bo <bo.liu@linux.alibaba.com>
> > Cc: <stable@vger.kernel.org> [4.9]
> > Signed-off-by: Minchan Kim <minchan@kernel.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.

Thanks.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 12:12   ` Minchan Kim
@ 2019-02-13 12:24     ` Michal Hocko
  2019-02-14  7:25       ` Minchan Kim
  0 siblings, 1 reply; 11+ messages in thread
From: Michal Hocko @ 2019-02-13 12:24 UTC (permalink / raw)
  To: Minchan Kim
  Cc: gregkh, linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Andrew Morton, Hugh Dickins, Liu Bo, stable

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@cmpxchg.org>
> > > Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > > Cc: Michal Hocko <mhocko@suse.com>
> > > Cc: Andrew Morton <akpm@linux-foundation.org>
> > > Cc: Hugh Dickins <hughd@google.com>
> > > Cc: Liu Bo <bo.liu@linux.alibaba.com>
> > > Cc: <stable@vger.kernel.org> [4.9]
> > > Signed-off-by: Minchan Kim <minchan@kernel.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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 11:29 [PATCH] mm: Fix the pgtable leak Minchan Kim
  2019-02-13 11:33 ` Minchan Kim
  2019-02-13 12:03 ` Michal Hocko
@ 2019-02-13 13:36 ` Greg KH
  2019-02-14  7:23   ` Minchan Kim
  2019-02-18 13:33 ` Greg KH
  3 siblings, 1 reply; 11+ messages in thread
From: Greg KH @ 2019-02-13 13:36 UTC (permalink / raw)
  To: Minchan Kim
  Cc: linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Michal Hocko, Andrew Morton, Hugh Dickins, Liu Bo, stable

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] 5cf3e5ff95876, mm, memcg: fix reclaim deadlock with writeback

This is really commit 63f3655f9501 ("mm, memcg: fix reclaim deadlock
with writeback") which was in 4.9.152, 4.14.94, 4.19.16, and 4.20.3 as
well as 5.0-rc2.

> [2] b0b9b3df27d10, mm: stop leaking PageTables

This commit was in 4.10, so I am guessing that this really is just a
backport of that commit?

If so, it's not the full backport, why not take the whole thing?  Why
only cherry-pick one chunk of it?  Why do we not need the other parts?

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 13:36 ` Greg KH
@ 2019-02-14  7:23   ` Minchan Kim
  2019-02-18  8:20     ` Minchan Kim
  0 siblings, 1 reply; 11+ messages in thread
From: Minchan Kim @ 2019-02-14  7:23 UTC (permalink / raw)
  To: Greg KH
  Cc: linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Michal Hocko, Andrew Morton, Hugh Dickins, Liu Bo, stable

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.
> > To fix the problem, this patch backport [2].
> > 
> > [1] 5cf3e5ff95876, mm, memcg: fix reclaim deadlock with writeback
> 
> This is really commit 63f3655f9501 ("mm, memcg: fix reclaim deadlock
> with writeback") which was in 4.9.152, 4.14.94, 4.19.16, and 4.20.3 as
> well as 5.0-rc2.

Since 4.10, we has [2] so it should be okay other (tree > 4.10)

> 
> > [2] b0b9b3df27d10, mm: stop leaking PageTables
> 
> This commit was in 4.10, so I am guessing that this really is just a
> backport of that commit?

Yub.

> 
> If so, it's not the full backport, why not take the whole thing?  Why
> only cherry-pick one chunk of it?  Why do we not need the other parts?

Because [2] actually aims for fixing [3] which was introduced at 4.10.
Since then, [1] relies on the chunk I sent. Thus we don't need other part
for 4.9.

[3] 953c66c2b22a ("mm: THP page cache support for ppc64")

Thanks.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 12:24     ` Michal Hocko
@ 2019-02-14  7:25       ` Minchan Kim
  0 siblings, 0 replies; 11+ messages in thread
From: Minchan Kim @ 2019-02-14  7:25 UTC (permalink / raw)
  To: Michal Hocko
  Cc: gregkh, linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Andrew Morton, Hugh Dickins, Liu Bo, stable

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
> > > > 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@cmpxchg.org>
> > > > Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > > > Cc: Michal Hocko <mhocko@suse.com>
> > > > Cc: Andrew Morton <akpm@linux-foundation.org>
> > > > Cc: Hugh Dickins <hughd@google.com>
> > > > Cc: Liu Bo <bo.liu@linux.alibaba.com>
> > > > Cc: <stable@vger.kernel.org> [4.9]
> > > > Signed-off-by: Minchan Kim <minchan@kernel.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.

Yub, I think only 4.9 stable tree need to be fixed because Hugh's patch was
in there since v4.10. 

Thanks.

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-14  7:23   ` Minchan Kim
@ 2019-02-18  8:20     ` Minchan Kim
  2019-02-18  8:33       ` Greg KH
  0 siblings, 1 reply; 11+ messages in thread
From: Minchan Kim @ 2019-02-18  8:20 UTC (permalink / raw)
  To: Greg KH
  Cc: linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Michal Hocko, Andrew Morton, Hugh Dickins, Liu Bo, stable

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 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
> > 
> > This is really commit 63f3655f9501 ("mm, memcg: fix reclaim deadlock
> > with writeback") which was in 4.9.152, 4.14.94, 4.19.16, and 4.20.3 as
> > well as 5.0-rc2.
> 
> Since 4.10, we has [2] so it should be okay other (tree > 4.10)
> 
> > 
> > > [2] b0b9b3df27d10, mm: stop leaking PageTables
> > 
> > This commit was in 4.10, so I am guessing that this really is just a
> > backport of that commit?
> 
> Yub.
> 
> > 
> > If so, it's not the full backport, why not take the whole thing?  Why
> > only cherry-pick one chunk of it?  Why do we not need the other parts?
> 
> Because [2] actually aims for fixing [3] which was introduced at 4.10.
> Since then, [1] relies on the chunk I sent. Thus we don't need other part
> for 4.9.
> 
> [3] 953c66c2b22a ("mm: THP page cache support for ppc64")

Hi Greg,

Any chance to look into this patch?

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-18  8:20     ` Minchan Kim
@ 2019-02-18  8:33       ` Greg KH
  0 siblings, 0 replies; 11+ messages in thread
From: Greg KH @ 2019-02-18  8:33 UTC (permalink / raw)
  To: Minchan Kim
  Cc: linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Michal Hocko, Andrew Morton, Hugh Dickins, Liu Bo, stable

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 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
> > > 
> > > This is really commit 63f3655f9501 ("mm, memcg: fix reclaim deadlock
> > > with writeback") which was in 4.9.152, 4.14.94, 4.19.16, and 4.20.3 as
> > > well as 5.0-rc2.
> > 
> > Since 4.10, we has [2] so it should be okay other (tree > 4.10)
> > 
> > > 
> > > > [2] b0b9b3df27d10, mm: stop leaking PageTables
> > > 
> > > This commit was in 4.10, so I am guessing that this really is just a
> > > backport of that commit?
> > 
> > Yub.
> > 
> > > 
> > > If so, it's not the full backport, why not take the whole thing?  Why
> > > only cherry-pick one chunk of it?  Why do we not need the other parts?
> > 
> > Because [2] actually aims for fixing [3] which was introduced at 4.10.
> > Since then, [1] relies on the chunk I sent. Thus we don't need other part
> > for 4.9.
> > 
> > [3] 953c66c2b22a ("mm: THP page cache support for ppc64")
> 
> Hi Greg,
> 
> Any chance to look into this patch?

You sent it on Thursday, it is Monday, I tried to actually take the
weekend off :)

It's in my queue, relax, it has good company with a few other hundred
stable patches being requested...

greg k-h

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: [PATCH] mm: Fix the pgtable leak
  2019-02-13 11:29 [PATCH] mm: Fix the pgtable leak Minchan Kim
                   ` (2 preceding siblings ...)
  2019-02-13 13:36 ` Greg KH
@ 2019-02-18 13:33 ` Greg KH
  3 siblings, 0 replies; 11+ messages in thread
From: Greg KH @ 2019-02-18 13:33 UTC (permalink / raw)
  To: Minchan Kim
  Cc: linux-mm, LKML, Johannes Weiner, Kirill A . Shutemov,
	Michal Hocko, Andrew Morton, Hugh Dickins, Liu Bo, stable

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] 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@cmpxchg.org>
> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Liu Bo <bo.liu@linux.alibaba.com>
> Cc: <stable@vger.kernel.org> [4.9]
> Signed-off-by: Minchan Kim <minchan@kernel.org>
> ---
>  mm/memory.c | 21 +++++++++++++++------
>  1 file changed, 15 insertions(+), 6 deletions(-)

I fixed up the changelog text to be correct, and now queued this up,
thanks.

greg k-h

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2019-02-18 13:33 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-13 11:29 [PATCH] mm: Fix the pgtable leak Minchan Kim
2019-02-13 11:33 ` Minchan Kim
2019-02-13 12:03 ` Michal Hocko
2019-02-13 12:12   ` Minchan Kim
2019-02-13 12:24     ` Michal Hocko
2019-02-14  7:25       ` Minchan Kim
2019-02-13 13:36 ` Greg KH
2019-02-14  7:23   ` Minchan Kim
2019-02-18  8:20     ` Minchan Kim
2019-02-18  8:33       ` Greg KH
2019-02-18 13:33 ` Greg KH

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).