From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751714AbcGPOKd (ORCPT ); Sat, 16 Jul 2016 10:10:33 -0400 Received: from mail-sn1nam02on0053.outbound.protection.outlook.com ([104.47.36.53]:26784 "EHLO NAM02-SN1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751540AbcGPOKa convert rfc822-to-8bit (ORCPT ); Sat, 16 Jul 2016 10:10:30 -0400 X-Greylist: delayed 67343 seconds by postgrey-1.27 at vger.kernel.org; Sat, 16 Jul 2016 10:10:30 EDT From: Jens Rottmann To: Lukasz Odzioba , Sasha Levin CC: "stable@vger.kernel.org" , Michal Hocko , "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" Thread-Topic: 4.1.28: memory leak introduced by "mm/swap.c: flush lru pvecs on compound page arrival" Thread-Index: AQHR3tIHQmwC8F1JtkapS+5ShFIzSqAbEKTg Date: Sat, 16 Jul 2016 13:55:44 +0000 Message-ID: References: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com> In-Reply-To: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=jens.rottmann@adlinktech.com; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [79.223.72.142] x-ms-office365-filtering-correlation-id: 6a5d8166-26a4-4e7d-5363-08d3ad80e212 x-microsoft-exchange-diagnostics: 1;BLUPR0501MB2082;6:+Yrn+jcVsGMvk+7P7kP2ZEuxOgmakomPEKWVNhWYrj/gu5Uo+esusQmHLUg7K112MfHG1xMNGfkIx0q0HvxhFeo2fRAirCYzKI/DM5/SYrE3V8UQPvJ/WuODnl0626RSeHXGlIhYMccAqnJrU0V8Xeg7qkcGp2x2sjc9f74azxvYKMk9s+5yEY+TF/sA+hfte9sUMsFGRhSlCVGWaTecw9Cl4pbeVgMdjWQoFrdLIqt8biDrZypCFrVh5HGNlquSBVb7too36YBof3N3D0o8thbg/7AaiXg+kzoEC38AjGI=;5:Nuw569YNr8f6Mck9H9qUYgPYp6hyM3GckoYE26golyRdbAxl5i/S2ALPTyEOR9tIVQ/YwLkYv6FAjrp+nxbsFLuUMxrCilrE4+AftCJmRyXmiYwptjDW74L3qYFjskilZ3sDvVMNPLLgiagBGP6uRg==;24:YAtz7nK7e9T0wR6g8hW+bcCAFf9Q++mzCmHUTRp755j7b9zZqRj6VoppZmXsiG0A1HxrS0ZeXGVcn7WEWDJ2pF2LEYx2XQmvOLMqO7GoX7k=;7:5kkZXHd8wj3lAC+hlEopKamYJtzkO06NmdRs5hoWde8ubOxFTS3EgSIulKthcoB2nep4mxKUjR7ghXVYMlQyKrK+/O6IZRw5OqIG9VZ/akKnTvXh39jpYEXzvCo3eg6WacTec8L0FD4I9oNIqnvw9slh8i/vCqeSsLJoEx0pU+jzD5etmRIhYFYYuvo7wRUjRwrCbh8Rih502HqNhfvGTHeySBzE6MSgTlvuGtiaN4EW0h4YgQsmKFILytOsg1Yn x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB2082; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(9452136761055)(101931422205132); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001);SRVR:BLUPR0501MB2082;BCL:0;PCL:0;RULEID:;SRVR:BLUPR0501MB2082; x-forefront-prvs: 0005B05917 x-forefront-antispam-report: SFV:NSPM;SFS:(10009020)(6009001)(7916002)(189002)(199003)(5423002)(9686002)(66066001)(99286002)(54356999)(68736007)(76176999)(4326007)(105586002)(189998001)(50986999)(6116002)(74316002)(101416001)(11100500001)(7696003)(2906002)(7846002)(8936002)(5003600100003)(305945005)(10400500002)(92566002)(19580405001)(3900700001)(5002640100001)(8676002)(33656002)(7736002)(81166006)(81156014)(3660700001)(5001770100001)(2900100001)(19580395003)(87936001)(76576001)(97736004)(102836003)(106356001)(86362001)(122556002)(2950100001)(3280700002)(586003)(3846002)(106116001)(77096005);DIR:OUT;SFP:1101;SCL:1;SRVR:BLUPR0501MB2082;H:BLUPR0501MB2082.namprd05.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:3;A:3;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT MIME-Version: 1.0 X-OriginatorOrg: adlinktech.com X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jul 2016 13:55:44.5539 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 6c7b546b-78e1-414f-8297-48bb0f8ca053 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR0501MB2082 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi again, took lack of response to express reluctance examining vendor kernels. Therefore reproduced and can confirm memory leak on 4.1.28 vanilla x86. Identical symptoms. Regards, Jens ________________________________________ From: Jens Rottmann Sent: Friday, July 15, 2016 21:27 To: Lukasz Odzioba; Sasha Levin Cc: stable@vger.kernel.org; Michal Hocko; linux-mm@kvack.org; linux-kernel@vger.kernel.org Subject: 4.1.28: memory leak introduced by "mm/swap.c: flush lru pvecs on compound page arrival" Hi, 4.1.y stable commit c5ad33184354260be6d05de57e46a5498692f6d6 (Upstream commit 8f182270dfec432e93fae14f9208a6b9af01009f) "mm/swap.c: flush lru pvecs on compound page arrival" in 4.1.28 introduces a memory leak. Simply running while sleep 0.1; do clear; free; done shows mem continuously going down, eventually system panics with no killable processes left. Replacing "sleep" with "unxz -t some.xz" brings system down within minutes. Kmemleak did not report anything. Bisect ended at named commit, and reverting only this commit is indeed sufficient to fix the leak. Swap partition on/off makes no difference. My set-up: i.MX6 (ARM Cortex-A9) dual-core, 2 GB RAM. Kernel sources are from git.freescale.com i.e. heavily modified by Freescale for i.MX SoCs, kernel.org stable patches up to 4.1.28 manually added. I tried to reproduce with vanilla 4.1.28, but that wouldn't boot at all on my i.MX hardware, hangs immediately after "Starting kernel", sorry. However there is not a single difference between Freescale and vanilla in the whole mm/ subdirectory, so I don't think it's i.MX-specific. I didn't cross-check with an x86 system (yet). Regards, Jens From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Jens Rottmann To: Lukasz Odzioba , Sasha Levin CC: "stable@vger.kernel.org" , Michal Hocko , "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 13:55:44 +0000 Message-ID: References: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com> In-Reply-To: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com> Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-linux-mm@kvack.org List-ID: Hi again, took lack of response to express reluctance examining vendor kernels. There= fore reproduced and can confirm memory leak on 4.1.28 vanilla x86. Identica= l symptoms. Regards, Jens ________________________________________ From: Jens Rottmann Sent: Friday, July 15, 2016 21:27 To: Lukasz Odzioba; Sasha Levin Cc: stable@vger.kernel.org; Michal Hocko; linux-mm@kvack.org; linux-kernel@= vger.kernel.org Subject: 4.1.28: memory leak introduced by "mm/swap.c: flush lru pvecs on c= ompound page arrival" Hi, 4.1.y stable commit c5ad33184354260be6d05de57e46a5498692f6d6 (Upstream commit 8f182270dfec432e93fae14f9208a6b9af01009f) "mm/swap.c: flush lru pvecs on compound page arrival" in 4.1.28 introduces a memory leak. Simply running while sleep 0.1; do clear; free; done shows mem continuously going down, eventually system panics with no killable processes left. Replacing "sleep" with "unxz -t some.xz" brings system down within minutes. Kmemleak did not report anything. Bisect ended at named commit, and reverting only this commit is indeed sufficient to fix the leak. Swap partition on/off makes no difference. My set-up: i.MX6 (ARM Cortex-A9) dual-core, 2 GB RAM. Kernel sources are from git.freescale.com i.e. heavily modified by Freescale for i.MX SoCs, kernel.org stable patches up to 4.1.28 manually added. I tried to reproduce with vanilla 4.1.28, but that wouldn't boot at all on my i.MX hardware, hangs immediately after "Starting kernel", sorry. However there is not a single difference between Freescale and vanilla in the whole mm/ subdirectory, so I don't think it's i.MX-specific. I didn't cross-check with an x86 system (yet). Regards, Jens -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org