From: Christoph Lameter <cl@linux.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Michal Hocko <mhocko@suse.cz>, Pekka Enberg <penberg@kernel.org>,
Matt Mackall <mpm@selenic.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: slub: gpf in deactivate_slab
Date: Tue, 25 Mar 2014 13:10:55 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1403251308590.26471@nuc> (raw)
In-Reply-To: <5331B9C8.7080106@oracle.com>
On Tue, 25 Mar 2014, Sasha Levin wrote:
> So here's the full trace. There's obviously something wrong here since we
> pagefault inside the section that was supposed to be running with irqs
> disabled
> and I don't see another cause besides this.
>
> The unreliable entries in the stack trace also somewhat suggest that the
> fault is with the code I've pointed out.
Looks like there was some invalid data fed to the function and the page
fault with interrupts disabled is the result of following and invalid
pointer.
Is there more context information available? What are the options set for
the cache that the operation was performed on?
--
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>
next prev parent reply other threads:[~2014-03-25 18:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 16:25 Sasha Levin
2014-03-25 15:54 ` Sasha Levin
2014-03-25 16:51 ` Christoph Lameter
2014-03-25 16:52 ` Michal Hocko
2014-03-25 17:06 ` Christoph Lameter
2014-03-25 17:15 ` Sasha Levin
2014-03-25 18:10 ` Christoph Lameter [this message]
2014-03-26 0:17 ` Sasha Levin
2014-03-26 15:43 ` Christoph Lameter
2014-04-05 15:20 ` Sasha Levin
2014-04-07 17:13 ` Christoph Lameter
2014-04-07 17:16 ` Sasha Levin
2014-04-07 19:34 ` Christoph Lameter
2014-03-25 17:56 ` Michal Hocko
2014-03-25 18:01 ` Michal Hocko
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.DEB.2.10.1403251308590.26471@nuc \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mpm@selenic.com \
--cc=penberg@kernel.org \
--cc=sasha.levin@oracle.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