From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754748AbaCYSLA (ORCPT ); Tue, 25 Mar 2014 14:11:00 -0400 Received: from qmta04.emeryville.ca.mail.comcast.net ([76.96.30.40]:43140 "EHLO qmta04.emeryville.ca.mail.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754708AbaCYSK6 (ORCPT ); Tue, 25 Mar 2014 14:10:58 -0400 Date: Tue, 25 Mar 2014 13:10:55 -0500 (CDT) From: Christoph Lameter X-X-Sender: cl@nuc To: Sasha Levin cc: Michal Hocko , Pekka Enberg , Matt Mackall , "linux-mm@kvack.org" , LKML Subject: Re: mm: slub: gpf in deactivate_slab In-Reply-To: <5331B9C8.7080106@oracle.com> Message-ID: References: <53208A87.2040907@oracle.com> <5331A6C3.2000303@oracle.com> <20140325165247.GA7519@dhcp22.suse.cz> <5331B9C8.7080106@oracle.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?