stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	stable <stable@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] 4.1.28 Fix bad backport of 8f182270dfec "mm/swap.c: flush lru pvecs on compound page arrival"
Date: Fri, 15 Jul 2016 08:55:05 +0200	[thread overview]
Message-ID: <20160715065504.GA11811@dhcp22.suse.cz> (raw)
In-Reply-To: <20160714175521.3675e3d6@gandalf.local.home>

On Thu 14-07-16 17:55:21, Steven Rostedt wrote:
> When I pulled in 4.1.28 into my stable 4.1-rt tree and ran the tests,
> it crashed with a severe OOM killing everything. I then tested 4.1.28
> without -rt and it had the same issue. I did a bisect between 4.1.27
> and 4.1.28 and found that the bug started at:
> 
> commit 8f182270dfec "mm/swap.c: flush lru pvecs on compound page
> arrival"
> 
> Looking at that patch and what's in mainline, I see that there's a
> mismatch in one of the hunks:
> 
> Mainline:
> 
> @@ -391,9 +391,8 @@ static void __lru_cache_add(struct page *page)
>         struct pagevec *pvec = &get_cpu_var(lru_add_pvec);
> 
>         get_page(page);
> -       if (!pagevec_space(pvec))
> +       if (!pagevec_add(pvec, page) || PageCompound(page))
>                 __pagevec_lru_add(pvec);
> -       pagevec_add(pvec, page);
>         put_cpu_var(lru_add_pvec);
>  }
> 
> 
> Stable 4.1.28:
> 
> @@ -631,9 +631,8 @@ static void __lru_cache_add(struct page *page)
>         struct pagevec *pvec = &get_cpu_var(lru_add_pvec);
> 
>         page_cache_get(page);
> -       if (!pagevec_space(pvec))
> +       if (!pagevec_space(pvec) || PageCompound(page))
>                 __pagevec_lru_add(pvec);
> -       pagevec_add(pvec, page);
>         put_cpu_var(lru_add_pvec);
>  }

Heh, I've made the same mistake when backporting this to our older SLES
based kernel initially. I was lucky the system even didn't boot. Sorry
that I didn't find time to review the stable backport.

> Where mainline replace pagevec_space() with pagevec_add, and stable did
> not.
> 
> Fixing this makes the OOM go away.
> 
> Note, 3.18 has the same bug.
> 
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

Acked-by: Michal Hocko <mhocko@suse.com>

> ---
> diff --git a/mm/swap.c b/mm/swap.c
> index b523f0a4cbfb..ab3b9c2dd783 100644
> --- a/mm/swap.c
> +++ b/mm/swap.c
> @@ -631,7 +631,7 @@ static void __lru_cache_add(struct page *page)
>  	struct pagevec *pvec = &get_cpu_var(lru_add_pvec);
>  
>  	page_cache_get(page);
> -	if (!pagevec_space(pvec) || PageCompound(page))
> +	if (!pagevec_add(pvec, page) || PageCompound(page))
>  		__pagevec_lru_add(pvec);
>  	put_cpu_var(lru_add_pvec);
>  }

-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2016-07-15  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-14 21:55 [PATCH] 4.1.28 Fix bad backport of 8f182270dfec "mm/swap.c: flush lru pvecs on compound page arrival" Steven Rostedt
2016-07-15  6:55 ` Michal Hocko [this message]
2016-07-15 11:51   ` Sasha Levin

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=20160715065504.GA11811@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=rostedt@goodmis.org \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.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).