From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail-bn3nam01on0062.outbound.protection.outlook.com ([104.47.33.62]:28073
	"EHLO NAM01-BN3-obe.outbound.protection.outlook.com"
	rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
	id S1753323AbcGSOzW (ORCPT <rfc822;stable@vger.kernel.org>);
	Tue, 19 Jul 2016 10:55:22 -0400
Subject: Re: 3.18.37 broken / memory leak
References: <83d21ffc-eeb8-40f8-7443-8d8291cd5973@ADLINKtech.com>
 <20160716144740.GA29708@bbox>
CC: Sasha Levin <sasha.levin@oracle.com>, <stable@vger.kernel.org>
To: Sebastian Gottschall <S.Gottschall@dd-wrt.com>
From: Jens Rottmann <Jens.Rottmann@ADLINKtech.com>
Message-ID: <1361ec8d-b7ed-8cff-7c00-32d0afd729ac@ADLINKtech.com>
Date: Tue, 19 Jul 2016 16:22:23 +0200
MIME-Version: 1.0
In-Reply-To: <20160716144740.GA29708@bbox>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On 07/18/2016 14:21, Sebastian Gottschall wrote:
> the kernel contains a big memory leak likelly within the
> network stack. each tcp packet consumes memory. on a
> embedded system a small scp transfer causes a oom after
> seconds. and reboots the system since init was killed.

Sounds like you might have hit the same leak in 3.18.37 that Steven
Rostedt and others found in 4.1.28?

http://article.gmane.org/gmane.linux.kernel.stable/184384

Cheers,
Jens