Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263638AbTENSwN (ORCPT ); Wed, 14 May 2003 14:52:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263645AbTENSwN (ORCPT ); Wed, 14 May 2003 14:52:13 -0400 Received: from nat-pool-bos.redhat.com ([66.187.230.200]:42374 "EHLO chimarrao.boston.redhat.com") by vger.kernel.org with ESMTP id S263638AbTENSwI (ORCPT ); Wed, 14 May 2003 14:52:08 -0400 Date: Wed, 14 May 2003 15:04:55 -0400 (EDT) From: Rik van Riel X-X-Sender: riel@chimarrao.boston.redhat.com To: Andrew Morton cc: Dave McCracken , , , Subject: Re: Race between vmtruncate and mapped areas? In-Reply-To: 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: 924 Lines: 24 On Wed, 14 May 2003, Rik van Riel wrote: > On Wed, 14 May 2003, Andrew Morton wrote: > > > It would be nice to make them go away - they cause problems. > > 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. Which means a security bug, as well as the potential to end up with bad pointers in kernel space, eg. think about the rmap code jumping to a no longer existing mm_struct. The more I think about it, the more I agree with Andrew that it would be really really nice to get rid of them ;) - 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/