All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Rottmann <Jens.Rottmann@ADLINKtech.com>
To: Lukasz Odzioba <lukasz.odzioba@intel.com>,
	Sasha Levin <sasha.levin@oracle.com>
Cc: <stable@vger.kernel.org>, Michal Hocko <mhocko@suse.com>,
	<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: Re: 4.1.28: memory leak introduced by "mm/swap.c: flush lru pvecs on compound page arrival"
Date: Sat, 16 Jul 2016 00:33:25 +0200	[thread overview]
Message-ID: <99545b9a-9b3d-6e97-f2cd-7a274cca1521@ADLINKtech.com> (raw)
In-Reply-To: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com>

[-- Attachment #1: Type: text/plain, Size: 54 bytes --]

Attached my .config, in case that helps.
Cheers, Jens

[-- Attachment #2: config.xz --]
[-- Type: application/x-xz, Size: 18448 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Jens Rottmann <Jens.Rottmann@ADLINKtech.com>
To: Lukasz Odzioba <lukasz.odzioba@intel.com>,
	Sasha Levin <sasha.levin@oracle.com>
Cc: stable@vger.kernel.org, Michal Hocko <mhocko@suse.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: 4.1.28: memory leak introduced by "mm/swap.c: flush lru pvecs on compound page arrival"
Date: Sat, 16 Jul 2016 00:33:25 +0200	[thread overview]
Message-ID: <99545b9a-9b3d-6e97-f2cd-7a274cca1521@ADLINKtech.com> (raw)
In-Reply-To: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com>

[-- Attachment #1: Type: text/plain, Size: 54 bytes --]

Attached my .config, in case that helps.
Cheers, Jens

[-- Attachment #2: config.xz --]
[-- Type: application/x-xz, Size: 18448 bytes --]

  reply	other threads:[~2016-07-15 22:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 19:27 4.1.28: memory leak introduced by "mm/swap.c: flush lru pvecs on compound page arrival" Jens Rottmann
2016-07-15 19:27 ` Jens Rottmann
2016-07-15 19:27 ` Jens Rottmann
2016-07-15 22:33 ` Jens Rottmann [this message]
2016-07-15 22:33   ` Jens Rottmann
2016-07-16 13:55 ` Jens Rottmann
2016-07-16 13:55   ` Jens Rottmann
2016-07-16 14:47 ` Minchan Kim
2016-07-16 14:47   ` Minchan Kim
2016-07-16 14:47   ` Minchan Kim
2016-07-16 17:29   ` Jens Rottmann
2016-07-16 17:29     ` Jens Rottmann
2016-07-16 18:48     ` Mikulas Patocka
2016-07-16 18:48       ` Mikulas Patocka
2016-07-18  6:53   ` Michal Hocko
2016-07-18  6:53     ` Michal Hocko
2016-07-19 14:22   ` 3.18.37 broken / memory leak Jens Rottmann
2016-07-19 16:51     ` Sebastian Gottschall

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=99545b9a-9b3d-6e97-f2cd-7a274cca1521@ADLINKtech.com \
    --to=jens.rottmann@adlinktech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lukasz.odzioba@intel.com \
    --cc=mhocko@suse.com \
    --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 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.