From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 23 Apr 2008 11:19:26 -0700 (PDT) From: Christoph Lameter Subject: Re: [PATCH 01 of 12] Core of mmu notifiers In-Reply-To: <20080423163713.GC24536@duo.random> Message-ID: References: <20080422223545.GP24536@duo.random> <20080422230727.GR30298@sgi.com> <20080423002848.GA32618@sgi.com> <20080423163713.GC24536@duo.random> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Andrea Arcangeli Cc: Jack Steiner , Robin Holt , Nick Piggin , Peter Zijlstra , kvm-devel@lists.sourceforge.net, Kanoj Sarcar , Roland Dreier , Steve Wise , linux-kernel@vger.kernel.org, Avi Kivity , linux-mm@kvack.org, general@lists.openfabrics.org, Hugh Dickins , akpm@linux-foundation.org, Rusty Russell List-ID: On Wed, 23 Apr 2008, Andrea Arcangeli wrote: > The only way to avoid failing because of vmalloc space shortage or > oom, would be to provide a O(N*N) fallback. But one that can't be > interrupted by sigkill! sigkill interruption was ok in #v12 because we > didn't rely on mmu_notifier_unregister to succeed. So it avoided any > DoS but it still can't provide any reliable unregister. If unregister fails then the driver should not detach from the address space immediately but wait until -->release is called. That may be a possible solution. It will be rare that the unregister fails. -- 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