From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753317AbYDPSfs (ORCPT ); Wed, 16 Apr 2008 14:35:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751099AbYDPSfk (ORCPT ); Wed, 16 Apr 2008 14:35:40 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:59834 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750932AbYDPSfj (ORCPT ); Wed, 16 Apr 2008 14:35:39 -0400 Date: Wed, 16 Apr 2008 11:35:38 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Robin Holt cc: Andrea Arcangeli , 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, Avi Kivity , kvm-devel@lists.sourceforge.net, general@lists.openfabrics.org, Hugh Dickins Subject: Re: [PATCH 1 of 9] Lock the entire mm to prevent any mmu related operation to happen In-Reply-To: <20080416163337.GJ22493@sgi.com> Message-ID: References: <20080416163337.GJ22493@sgi.com> MIME-Version: 1.0 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 Wed, 16 Apr 2008, Robin Holt wrote: > I don't think this lock mechanism is completely working. I have > gotten a few failures trying to dereference 0x100100 which appears to > be LIST_POISON1. How does xpmem unregistering of notifiers work?