From: Jens Rottmann <Jens.Rottmann@ADLINKtech.com>
To: Sebastian Gottschall <S.Gottschall@dd-wrt.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 16:22:23 +0200 [thread overview]
Message-ID: <1361ec8d-b7ed-8cff-7c00-32d0afd729ac@ADLINKtech.com> (raw)
In-Reply-To: <20160716144740.GA29708@bbox>
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
next prev parent reply other threads:[~2016-07-19 14:55 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 ` Jens Rottmann [this message]
2016-07-19 16:51 ` 3.18.37 broken / memory leak Sebastian Gottschall
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=1361ec8d-b7ed-8cff-7c00-32d0afd729ac@ADLINKtech.com \
--to=jens.rottmann@adlinktech.com \
--cc=S.Gottschall@dd-wrt.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.