linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Klaus Ethgen <Klaus+lkml@ethgen.de>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [KERNEL] Re: Bug 4.9 and memorymanagement
Date: Fri, 30 Dec 2016 17:52:30 +0100	[thread overview]
Message-ID: <20161230165230.th274as75pzjlzkk@ikki.ethgen.ch> (raw)
In-Reply-To: <20161230111135.GG13301@dhcp22.suse.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Sorry, did reply only you..

Am Fr den 30. Dez 2016 um 12:11 schrieb Michal Hocko:
> > If this turns out to be memory cgroup related then the patch from
> > http://lkml.kernel.org/r/20161226124839.GB20715@dhcp22.suse.cz might
> > help.
>
> Did you get chance to test the above patch? I would like to send it for
> merging and having it tested on another system would be really helpeful
> and much appreciated.

Sorry, no, I was a bit busy when coming back from X-mass. ;-)

Maybe I can do so today.

The only think is, how can I find out if the bug is fixed? Is 7 days
enough? Or is there a change to force the bug to happen (or not)...?

Am Fr den 30. Dez 2016 um 12:11 schrieb Michal Hocko:
> > If this turns out to be memory cgroup related then the patch from
> > http://lkml.kernel.org/r/20161226124839.GB20715@dhcp22.suse.cz might
> > help.

Which of the 3 patches is the one? All 3 or just one.

Regards
   Klaus
- -- 
Klaus Ethgen                                       http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16            Klaus Ethgen <Klaus@Ethgen.ch>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAlhmkM4ACgkQpnwKsYAZ
9qz18QwAtNNESyhqkpYaOss2Q6Ko1o+9eygil3X9MtAPWY/UP/d7MJ7q8lBrjQT7
wetFM4yZtfS4lk2wnUXUDHT8r41QT/39YmZefZemdHjMwbPk+NpeX3J7Y+Agu117
7x0NtWEpMM2mimSUcLpKxZjScx1lci572trlWVy8v8yPxTAeyPTxJ2Zun/W7vqS2
so3o2OA9eMSv7s0zWvE/9X3UZowcWaZtNIx2EvIPdghg2zazYwFydNFFGqn6tPtR
wlLj9Oxw3NTwKvFvHCGXz/xodw0t8Y1ZQa4yc5fYRzEy8PNJnxo6LNoboiycdcIw
E8FgybmJM2eFshiwRuFp8pgrI+HU6Mubp2aUPaNKYUUhfc58T59fSfh+qEkEkgym
kYCTiUA1f9SCSYVSkZrCaV1TuPnEmXANOTvQS5k4We7/kMbmk67UyWpSRCRSRYSX
Ofr/rblMVQ+dqQIQTVNoufSZgAOmCJdSbCQO/RduVjhSPgM47lLajIcRM/EYizE/
fBfHXomC
=T2Gd
-----END PGP SIGNATURE-----

  reply	other threads:[~2016-12-30 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-25 20:52 Bug 4.9 and memorymanagement Klaus Ethgen
2016-12-26 11:00 ` Michal Hocko
2016-12-27 11:28   ` Michal Hocko
2016-12-30 11:11     ` Michal Hocko
2016-12-30 16:52       ` Klaus Ethgen [this message]
2016-12-30 17:23         ` [KERNEL] " Michal Hocko
2017-01-04  8:06           ` Michal Hocko
2017-01-04  8:15             ` [KERNEL] " Klaus Ethgen
2017-01-04  8:31               ` Michal Hocko
2017-01-04  9:50                 ` [KERNEL] " Klaus Ethgen
     [not found]   ` <66baf7dd-c5e3-e11c-092f-3a642c306e63@I-love.SAKURA.ne.jp>
2016-12-27 11:48     ` Klaus Ethgen
2016-12-27 12:05       ` Michal Hocko
2016-12-27 12:14       ` Klaus Ethgen

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=20161230165230.th274as75pzjlzkk@ikki.ethgen.ch \
    --to=klaus+lkml@ethgen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).