From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751178AbeAPIhp (ORCPT + 1 other); Tue, 16 Jan 2018 03:37:45 -0500 Received: from mail-wr0-f178.google.com ([209.85.128.178]:38199 "EHLO mail-wr0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750816AbeAPIhn (ORCPT ); Tue, 16 Jan 2018 03:37:43 -0500 X-Google-Smtp-Source: ACJfBouo8vDCfOH3j7PRtZIhCa/o/BGAOLi9JbPdBr3qblEW/iKhf8txCFq5ycW3XN3eHCcnIh5Fgw== Date: Tue, 16 Jan 2018 09:37:39 +0100 From: Ingo Molnar To: Dave Hansen Cc: Linus Torvalds , Tetsuo Handa , Linux Kernel Mailing List , linux-mm , the arch/x86 maintainers , linux-fsdevel , Michal Hocko Subject: Re: [mm 4.15-rc8] Random oopses under memory pressure. Message-ID: <20180116083739.irw62va5kpc62cvr@gmail.com> References: <201801142054.FAD95378.LVOOFQJOFtMFSH@I-love.SAKURA.ne.jp> <201801160115.w0G1FOIG057203@www262.sakura.ne.jp> <7f100b0f-3588-be25-41f6-a0e4dde27916@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f100b0f-3588-be25-41f6-a0e4dde27916@linux.intel.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: * Dave Hansen wrote: > Did anyone else notice the > > [ 31.068198] ? vmalloc_sync_all+0x150/0x150 > > present in a bunch of the stack traces? That should be pretty uncommon. I thikn that's pretty unusual: > Is it just part of the normal do_page_fault() stack and the stack > dumper picks up on it? No, it should only be called by register_die_notifier(), which is not part of the regular stack dump, AFAICS. Thanks, Ingo From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 16 Jan 2018 09:37:39 +0100 From: Ingo Molnar To: Dave Hansen Cc: Linus Torvalds , Tetsuo Handa , Linux Kernel Mailing List , linux-mm , the arch/x86 maintainers , linux-fsdevel , Michal Hocko Subject: Re: [mm 4.15-rc8] Random oopses under memory pressure. Message-ID: <20180116083739.irw62va5kpc62cvr@gmail.com> References: <201801142054.FAD95378.LVOOFQJOFtMFSH@I-love.SAKURA.ne.jp> <201801160115.w0G1FOIG057203@www262.sakura.ne.jp> <7f100b0f-3588-be25-41f6-a0e4dde27916@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f100b0f-3588-be25-41f6-a0e4dde27916@linux.intel.com> Sender: owner-linux-mm@kvack.org List-ID: * Dave Hansen wrote: > Did anyone else notice the > > [ 31.068198] ? vmalloc_sync_all+0x150/0x150 > > present in a bunch of the stack traces? That should be pretty uncommon. I thikn that's pretty unusual: > Is it just part of the normal do_page_fault() stack and the stack > dumper picks up on it? No, it should only be called by register_die_notifier(), which is not part of the regular stack dump, AFAICS. Thanks, Ingo -- 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: email@kvack.org