linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Davidlohr Bueso <davidlohr@hp.com>, Linux MM <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@redhat.com>,
	Michel Lespinasse <walken@google.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	Oleg Nesterov <oleg@redhat.com>, Dave Jones <davej@redhat.com>
Subject: Re: [BUG] kernel BUG at mm/vmacache.c:85!
Date: Wed, 30 Apr 2014 20:56:40 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LSU.2.11.1404302030260.11435@eggly.anvils> (raw)
In-Reply-To: <53614BFE.9090804@linux.vnet.ibm.com>

On Thu, 1 May 2014, Srivatsa S. Bhat wrote:
> 
> I tried to recall the *exact* steps that I had carried out when I first
> hit the bug. I realized that I had actually used kexec to boot the new
> kernel. I had originally booted into a 3.7.7 kernel that happens to be
> on that machine, and then kexec()'ed 3.15-rc3 on it. And that had caused
> the kernel crash. Fresh boots of 3.15-rc3, as well as kexec from 3.15+
> to itself, seems to be pretty robust and has never resulted in any bad
> behavior (this is why I couldn't reproduce the issue earlier, since I was
> doing fresh boots of 3.15-rc).
> 
> So I tried the same recipe again (boot into 3.7.7 and kexec into 3.15-rc3+)
> and I got totally random crashes so far, once in sys_kill and two times in
> exit_mmap. So I guess the bug is in 3.7.x and probably 3.15-rc is fine after
> all...

I don't know if we can conclude the bug is in 3.7 rather than 3.15.

I spent a little while yesterday looking at your register dumps,
and applying scripts/decodecode to your Code lines.  I did notice a
pattern to the general protection faulting addresses, and the dumps
you show today confirm that pattern (but with "1e000000" at the top
instead of yesterday's "9e000000").

Sorry, I really cannot spend more time on this, but thought I should
at least throw out my observation before moving on.  Here I've simply
grepped out the lines with the significant pattern (and at least one
of these lines is essentially a repetition of the line before, value
moved from one register to another with offset subtracted; oh, and
that R12 line, "it" has been added on to the vsize acct_collect()
already accumulated).

RAX: 9e00000005f9e8fd RBX: 000000000000000b RCX: 0000000000000001
RAX: 9e00000005f9e5fd RBX: ffff881031a0c2f8 RCX: ffff88203d52ba40
RDX: 000000000000001e RSI: 9e00000005f9e5a5 RDI: ffff881031a0c2f8
R10: 0000000000000000 R11: 00000000000027d5 R12: 9e000000069d62fd
BUG: Bad page map in process kdump  pte:1e00000005f98701 pmd:1031489067
BUG: Bad page map in process kdump  pte:1e00000005f98701 pmd:103420b067
R13: 0000000000000004 R14: 1e00000005f93403 R15: 000000000000000a

That this corruption likes to attack mm structures (vmas yesterday,
page tables today) does make me wonder whether mm is to blame.

Hugh

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

  parent reply	other threads:[~2014-05-01  3:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-28 19:18 Srivatsa S. Bhat
2014-04-28 19:20 ` Srivatsa S. Bhat
2014-04-28 21:20 ` Linus Torvalds
2014-04-28 21:55   ` Linus Torvalds
2014-04-28 22:05     ` Hugh Dickins
2014-04-28 22:14       ` Davidlohr Bueso
2014-04-28 22:25         ` Linus Torvalds
2014-04-29  9:59           ` Srivatsa S. Bhat
2014-04-30 19:16             ` Srivatsa S. Bhat
2014-04-30 19:18               ` Srivatsa S. Bhat
2014-04-30 19:20                 ` Srivatsa S. Bhat
2014-04-30 20:26               ` Linus Torvalds
2014-05-01  3:56               ` Hugh Dickins [this message]
2014-04-28 22:39     ` Davidlohr Bueso
2014-04-28 22:58       ` Linus Torvalds
2014-04-28 23:11         ` Andrew Morton
2014-04-28 23:57           ` Linus Torvalds
2014-04-29  0:11             ` Davidlohr Bueso
2014-04-29 10:02               ` Srivatsa S. Bhat
2014-04-29 12:52                 ` [PATCH] vmacache: change vmacache_find() to always check ->vm_mm Oleg Nesterov
2014-04-29 13:09                   ` Srivatsa S. Bhat
2014-04-29 14:02                     ` Oleg Nesterov
2014-04-29 12:40               ` [BUG] kernel BUG at mm/vmacache.c:85! Oleg Nesterov
2014-04-29  8:02       ` Srivatsa S. Bhat
2014-04-29  7:59     ` Srivatsa S. Bhat
2014-04-29  0:00 ` Dave Jones
2014-04-29  8:21   ` Srivatsa S. Bhat

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=alpine.LSU.2.11.1404302030260.11435@eggly.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=davidlohr@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=oleg@redhat.com \
    --cc=riel@redhat.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=walken@google.com \
    /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