Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263658AbTENS7W (ORCPT ); Wed, 14 May 2003 14:59:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263660AbTENS7W (ORCPT ); Wed, 14 May 2003 14:59:22 -0400 Received: from nat-pool-bos.redhat.com ([66.187.230.200]:1672 "EHLO chimarrao.boston.redhat.com") by vger.kernel.org with ESMTP id S263658AbTENS7V (ORCPT ); Wed, 14 May 2003 14:59:21 -0400 Date: Wed, 14 May 2003 15:11:53 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Dave McCracken cc: Andrew Morton , , , Subject: Re: Race between vmtruncate and mapped areas? In-Reply-To: <127820000.1052939265@baldur.austin.ibm.com> Message-ID: 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: 869 Lines: 22 On Wed, 14 May 2003, Dave McCracken wrote: > --On Wednesday, May 14, 2003 15:04:55 -0400 Rik van Riel > wrote: > > >> Not to mention they could end up being outside of any VMA, > >> meaning there's no sane way to deal with them. > > > > I hate to follow up to my own email, but the fact that > > they're not in any VMA could mean we leak these pages > > at exit() time. > > Well, they are still inside the vma. Truncate doesn't shrink the vma. It > just generates SIGBUS when the app tries to fault the pages in. Right, I forgot about that. Forget the memory leak and security bug theory, then ;))) - 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/