All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
To: Michal Hocko <mhocko@kernel.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Kirill Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Vladimir Davydov <vdavydov@parallels.com>,
	Ming Li <mingli199x@qq.com>, Minchan Kim <minchan@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Sasha Levin <sasha.levin@oracle.com>
Subject: RE: Regression due to "mm/swap.c: flush lru pvecs on compound page arrival"
Date: Mon, 19 Dec 2016 18:53:09 +0000	[thread overview]
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC02505D52@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20161214152148.GO25573@dhcp22.suse.cz>

On Wednesday, December 14, 2016 4:22 PM Michal Hocko, wrote: 
> Ohh, I can see it now. This is not an upstream commit. This is a 3.18.37
> backport which was wrong! You need the follow up fix 52c84a95dc6a
> ("4.1.28 Fix bad backport of 8f182270dfec "mm/swap.c: flush lru pvecs on
> compound page arrival""). The primary problem was that __lru_cache_add
> has leaked pages which would explain your OOM.

Ian did it solve the problem for you?

Thanks,
Lukas



      reply	other threads:[~2016-12-19 18:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-14  8:34 [linux-3.18 bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 osstest service owner
2016-12-14 13:29 ` Regression due to "mm/swap.c: flush lru pvecs on compound page arrival" Ian Jackson
2016-12-14 13:29   ` Ian Jackson
2016-12-14 13:39   ` Michal Hocko
2016-12-14 15:14     ` Ian Jackson
2016-12-14 15:14       ` Ian Jackson
2016-12-14 16:46       ` Greg KH
2016-12-14 16:46         ` Greg KH
2016-12-14 16:58         ` Ian Jackson
2016-12-14 16:58           ` Ian Jackson
2016-12-14 15:21   ` Michal Hocko
2016-12-14 15:21     ` Michal Hocko
2016-12-19 18:53     ` Odzioba, Lukasz [this message]

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=D6EDEBF1F91015459DB866AC4EE162CC02505D52@IRSMSX103.ger.corp.intel.com \
    --to=lukasz.odzioba@intel.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ian.jackson@eu.citrix.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=mingli199x@qq.com \
    --cc=sasha.levin@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vdavydov@parallels.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.