From: Sasha Levin <sasha.levin@oracle.com>
To: Thomas Voegtle <tv@lio96.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>,
lwn@lwn.net, lukasz.odzioba@intel.com
Subject: Re: Linux 4.1.28
Date: Fri, 15 Jul 2016 07:54:25 -0400 [thread overview]
Message-ID: <5788CEF1.8010900@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1607151332380.5792@er-systems.de>
On 07/15/2016 07:38 AM, Thomas Voegtle wrote:
> On Wed, 13 Jul 2016, Sasha Levin wrote:
>
>> I'm announcing the release of the 4.1.28 kernel.
>
> I have a serious memleak with 4.1.28 (like 20mb/s)
> I stripped down my kernel config and started a bisect, which came to:
>
> # first bad commit: [c5ad33184354260be6d05de57e46a5498692f6d6] mm/swap.c:
> flush lru pvecs on compound page arrival
> =>
> commit c5ad33184354260be6d05de57e46a5498692f6d6
> Author: Lukasz Odzioba <lukasz.odzioba@intel.com>
> Date: Fri Jun 24 14:50:01 2016 -0700
>
> mm/swap.c: flush lru pvecs on compound page arrival
>
>
> Reverting this on top 4.1.28 helps. Config attached.
Yup, this was reported and a fix is already queued for 4.1.29.
Thanks,
Sasha
next prev parent reply other threads:[~2016-07-15 11:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 2:23 Linux 4.1.28 Sasha Levin
2016-07-14 17:58 ` Takashi Iwai
2016-07-15 11:38 ` Thomas Voegtle
2016-07-15 11:54 ` Sasha Levin [this message]
2016-07-15 13:04 ` Thomas Voegtle
2016-07-20 6:45 ` Arkadiusz Miskiewicz
2016-07-20 7:03 ` Arkadiusz Miskiewicz
2016-07-20 8:29 ` Michal Kubecek
2016-07-20 12:13 ` Thomas Voegtle
2016-08-02 16:14 ` Thomas Voegtle
2016-08-02 17:02 ` Michal Kubecek
2016-07-29 17:24 ` Josh Hunt
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=5788CEF1.8010900@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.odzioba@intel.com \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=tv@lio96.de \
/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