Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	Ingo Molnar <mingo@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Michal Hocko <mhocko@kernel.org>
Subject: Re: [mm 4.15-rc8] Random oopses under memory pressure.
Date: Tue, 16 Jan 2018 11:34:46 -0800	[thread overview]
Message-ID: <CA+55aFyxyjN0Mqnz66B4a0R+uR8DdfxdMhcg5rJVi8LwnpSRfA@mail.gmail.com> (raw)
In-Reply-To: <201801170233.JDG21842.OFOJMQSHtOFFLV@I-love.SAKURA.ne.jp>

On Tue, Jan 16, 2018 at 9:33 AM, Tetsuo Handa
<penguin-kernel@i-love.sakura.ne.jp> wrote:
>
> Since I got a faster reproducer, I tried full bisection between 4.11 and 4.12-rc1.
> But I have no idea why bisection arrives at c0332694903a37cf.

I don't think your reproducer is 100% reliable.

And bisection is great because it's very aggressive and optimal when
it comes to testing. But that also implies that if *any* of the
good/bad choices were incorrect, then the end result is pure garbage
and isn't even *close* to the right commit.

> It turned out that CONFIG_FLATMEM was irrelevant. I just did not hit it.

So have you actually been able to see the problem with FLATMEM, or is
this based on the bisect? Because I really think the bisect is pretty
much guaranteed to be wrong.

               Linus

--
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-16 19:34 UTC|newest]

Thread overview: 17+ 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         ` [mm? 4.15-rc7] " Tetsuo Handa
2018-01-11 14:21           ` Michal Hocko
2018-01-11 14:37             ` Tetsuo Handa
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 [this message]
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=CA+55aFyxyjN0Mqnz66B4a0R+uR8DdfxdMhcg5rJVi8LwnpSRfA@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mingo@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=x86@kernel.org \
    --subject='Re: [mm 4.15-rc8] 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).