Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@kernel.org
Cc: linux-mm@kvack.org, x86@kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [mm? 4.15-rc7] Random oopses under memory pressure.
Date: Thu, 11 Jan 2018 23:37:05 +0900	[thread overview]
Message-ID: <201801112337.HHB95897.JHQOFFtMOOVSFL@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20180111142148.GD1732@dhcp22.suse.cz>

Michal Hocko wrote:
> On Thu 11-01-18 23:11:12, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Wed 10-01-18 22:37:52, Tetsuo Handa wrote:
> > > > Michal Hocko wrote:
> > > > > On Wed 10-01-18 20:49:56, Tetsuo Handa wrote:
> > > > > > Tetsuo Handa wrote:
> > > > > > > I can hit this bug with Linux 4.11 and 4.8. (i.e. at least all 4.8+ have this bug.)
> > > > > > > So far I haven't hit this bug with Linux 4.8-rc3 and 4.7.
> > > > > > > Does anyone know what is happening?
> > > > > > 
> > > > > > I simplified the reproducer and succeeded to reproduce this bug with both
> > > > > > i7-2630QM (8 core) and i5-4440S (4 core). Thus, I think that this bug is
> > > > > > not architecture specific.
> > > > > 
> > > > > Can you see the same with 64b kernel?
> > > > 
> > > > No. I can hit this bug with only x86_32 kernels.
> > > > But if the cause is not specific to 32b, this might be silent memory corruption.
> > > > 
> > > > > It smells like a ref count imbalance and premature page free to me. Can
> > > > > you try to bisect this?
> > > > 
> > > > Too difficult to bisect, but at least I can hit this bug with 4.8+ kernels.
> > 
> > The bug in 4.8 kernel might be different from the bug in 4.15-rc7 kernel.
> > 4.15-rc7 kernel hits the bug so trivially.
> 
> Maybe you want to disable the oom reaper to reduce chances of some issue
> there.

I already tried it for 4.15-rc7.
The bug can occur before the OOM killer is invoked for the first time after boot.
The OOM killer and the OOM reaper are not the culprit.

--
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:[~2018-01-11 14:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201801091939.JDJ64598.HOMFQtOFSOVLFJ@I-love.SAKURA.ne.jp>
     [not found] ` <201801102049.BGJ13564.OOOMtJLSFQFVHF@I-love.SAKURA.ne.jp>
     [not found]   ` <20180110124519.GU1732@dhcp22.suse.cz>
     [not found]     ` <201801102237.BED34322.QOOJMFFFHVLSOt@I-love.SAKURA.ne.jp>
     [not found]       ` <20180111135721.GC1732@dhcp22.suse.cz>
2018-01-11 14:11         ` Tetsuo Handa
2018-01-11 14:21           ` Michal Hocko
2018-01-11 14:37             ` Tetsuo Handa [this message]
2018-01-12  1:31             ` [mm " Tetsuo Handa
2018-01-12  1:42               ` Linus Torvalds
2018-01-12 11:22                 ` Tetsuo Handa
2018-01-14 11:54                   ` Tetsuo Handa
2018-01-15 23:05                     ` Linus Torvalds
2018-01-16  1:15                       ` [mm 4.15-rc8] " Tetsuo Handa
2018-01-16  2:14                         ` Linus Torvalds
2018-01-16  8:06                           ` Dave Hansen
2018-01-16  8:37                             ` Ingo Molnar
2018-01-16 19:30                             ` Linus Torvalds
2018-01-16 17:33                           ` Tetsuo Handa
2018-01-16 19:34                             ` Linus Torvalds
2018-01-17 11:08                               ` Tetsuo Handa
2018-01-11 18:11           ` [mm? 4.15-rc7] " Linus Torvalds
2018-01-11 20:59             ` Tetsuo Handa

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=201801112337.HHB95897.JHQOFFtMOOVSFL@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=x86@kernel.org \
    --subject='Re: [mm? 4.15-rc7] Random oopses under memory pressure.' \
    /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

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).