Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753487AbbFOCrR (ORCPT ); Sun, 14 Jun 2015 22:47:17 -0400 Received: from mga03.intel.com ([134.134.136.65]:34462 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751961AbbFOCrN (ORCPT ); Sun, 14 Jun 2015 22:47:13 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,615,1427785200"; d="scan'208";a="508285549" From: Andi Kleen To: Oleg Nesterov Cc: Ingo Molnar , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andy Lutomirski , Andrew Morton , Denys Vlasenko , Brian Gerst , Peter Zijlstra , Borislav Petkov , "H. Peter Anvin" , Linus Torvalds , Thomas Gleixner , Waiman Long Subject: Re: why do we need vmalloc_sync_all? References: <1434188955-31397-1-git-send-email-mingo@kernel.org> <20150613185828.GA32376@redhat.com> <20150614075943.GA810@gmail.com> <20150614200623.GB19582@redhat.com> Date: Sun, 14 Jun 2015 19:47:11 -0700 In-Reply-To: <20150614200623.GB19582@redhat.com> (Oleg Nesterov's message of "Sun, 14 Jun 2015 22:06:23 +0200") Message-ID: <87bnghit74.fsf@tassilo.jf.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 697 Lines: 18 Oleg Nesterov writes: > > But again, the kernel no longer does this? do_page_fault() does vmalloc_fault() > without notify_die(). If it fails, I do not see how/why a modular DIE_OOPS > handler could try to resolve this problem and trigger another fault. The same problem can happen from NMI handlers or machine check handlers. It's not necessarily tied to page faults only. -Andi -- ak@linux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/