From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754439AbYDWRJg (ORCPT ); Wed, 23 Apr 2008 13:09:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752272AbYDWRJ1 (ORCPT ); Wed, 23 Apr 2008 13:09:27 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:52543 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751848AbYDWRJ0 (ORCPT ); Wed, 23 Apr 2008 13:09:26 -0400 Date: Wed, 23 Apr 2008 12:09:09 -0500 From: Jack Steiner To: Andrea Arcangeli Cc: Christoph Lameter , 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, Robin Holt , general@lists.openfabrics.org, Hugh Dickins , akpm@linux-foundation.org, Rusty Russell Subject: Re: [PATCH 01 of 12] Core of mmu notifiers Message-ID: <20080423170909.GA1459@sgi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org You may have spotted this already. If so, just ignore this. It looks like there is a bug in copy_page_range() around line 667. It's possible to do a mmu_notifier_invalidate_range_start(), then return -ENOMEM w/o doing a corresponding mmu_notifier_invalidate_range_end(). --- jack