From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755999AbYDHVrs (ORCPT ); Tue, 8 Apr 2008 17:47:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753999AbYDHVr3 (ORCPT ); Tue, 8 Apr 2008 17:47:29 -0400 Received: from bzq-179-150-194.static.bezeqint.net ([212.179.150.194]:39721 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753873AbYDHVr2 (ORCPT ); Tue, 8 Apr 2008 17:47:28 -0400 Message-ID: <47FBE7C9.9000701@qumranet.com> Date: Wed, 09 Apr 2008 00:46:49 +0300 From: Avi Kivity User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Andrea Arcangeli CC: Christoph Lameter , akpm@linux-foundation.org, Nick Piggin , Steve Wise , Peter Zijlstra , linux-mm@kvack.org, Kanoj Sarcar , Roland Dreier , Jack Steiner , linux-kernel@vger.kernel.org, kvm-devel@lists.sourceforge.net, Robin Holt , general@lists.openfabrics.org, Hugh Dickins Subject: Re: [PATCH 0 of 9] mmu notifier #v12 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrea Arcangeli wrote: > Note that mmu_notifier_unregister may also fail with -EINTR if there are > signal pending or the system runs out of vmalloc space or physical memory, > only exit_mmap guarantees that any kernel module can be unloaded in presence > of an oom condition. > > That's unusual. What happens to the notifier? Suppose I destroy a vm without exiting the process, what happens if it fires? -- Any sufficiently difficult bug is indistinguishable from a feature.