Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 12 Aug 2002 21:06:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 12 Aug 2002 21:06:10 -0400 Received: from garrincha.netbank.com.br ([200.203.199.88]:29197 "HELO garrincha.netbank.com.br") by vger.kernel.org with SMTP id ; Mon, 12 Aug 2002 21:06:10 -0400 Date: Mon, 12 Aug 2002 22:09:41 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Thomas Molina cc: linux-kernel@vger.kernel.org Subject: Re: pte_chain leak in rmap code (2.5.31) In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1022 Lines: 31 On Mon, 12 Aug 2002, Thomas Molina wrote: > On Mon, 12 Aug 2002, Rik van Riel wrote: > > On Mon, 12 Aug 2002, Christian Ehrhardt wrote: > > > > > Note the strange use of continue and break which both achieve the same! > > > What was meant to happen (judging from rmap-13c) is that we break > > Excellent hunting! Thank you! > Any chance this is the cause of the following? Yes, quite possible. > From: Adam Kropelin > Date: 2002-08-12 2:54:31 > But we do have a repeatable inconsistency happening with ntpd and > memory pressure. That may be related, but in that case it's probably > related to mlock(). kind regards, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ - 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/