linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Klaus Ethgen <Klaus+lkml@ethgen.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [KERNEL] Re: Bug 4.9 and memorymanagement
Date: Wed, 4 Jan 2017 09:06:40 +0100	[thread overview]
Message-ID: <20170104080639.GB25453@dhcp22.suse.cz> (raw)
In-Reply-To: <20161230172358.GA4266@dhcp22.suse.cz>

On Fri 30-12-16 18:23:58, Michal Hocko wrote:
> On Fri 30-12-16 17:52:30, Klaus Ethgen wrote:
> > 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)...?
> 
> Just try to run with the patch and do what you do normally. If you do
> not see any OOMs in few days it should be sufficient evidence. From your
> previous logs it seems you hit the problem quite early after few hours
> as far as I remember.

Did you have chance to run with the patch? I would like to post it for
inclusion and feedback from you is really useful.

Thanks!
-- 
Michal Hocko
SUSE Labs

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-01-04  8:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161225205251.nny6k5wol2s4ufq7@ikki.ethgen.ch>
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       ` [KERNEL] " Klaus Ethgen
2016-12-30 17:23         ` Michal Hocko
2017-01-04  8:06           ` Michal Hocko [this message]
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=20170104080639.GB25453@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=Klaus+lkml@ethgen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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