All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Jens Rottmann <Jens.Rottmann@ADLINKtech.com>
Cc: Sasha Levin <sasha.levin@oracle.com>, stable@vger.kernel.org
Subject: Re: 3.18.37 broken / memory leak
Date: Tue, 19 Jul 2016 18:51:12 +0200	[thread overview]
Message-ID: <be157558-087e-7a79-cacd-84987808fccd@dd-wrt.com> (raw)
In-Reply-To: <1361ec8d-b7ed-8cff-7c00-32d0afd729ac@ADLINKtech.com>

Am 19.07.2016 um 16:22 schrieb Jens Rottmann:
> 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
     yes an the solution fixed it. i validated it

Sebastian
>
> Cheers,
> Jens
>


-- 
Mit freundlichen Gr�ssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz:  Berliner Ring 101, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Gesch�ftsf�hrer: Peter Steinh�user, Christian Scheele
http://www.dd-wrt.com
email: s.gottschall@dd-wrt.com
Tel.: +496251-582650 / Fax: +496251-5826565


  reply	other threads:[~2016-07-19 16:51 UTC|newest]

Thread overview: 20+ 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
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 [this message]
2016-07-18 14:06 Sebastian Gottschall
2016-07-18 14:21 ` 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=be157558-087e-7a79-cacd-84987808fccd@dd-wrt.com \
    --to=s.gottschall@dd-wrt.com \
    --cc=Jens.Rottmann@ADLINKtech.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.