Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964845AbWBMUEZ (ORCPT ); Mon, 13 Feb 2006 15:04:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964846AbWBMUEY (ORCPT ); Mon, 13 Feb 2006 15:04:24 -0500 Received: from [194.90.237.34] ([194.90.237.34]:2240 "EHLO mtlexch01.mtl.com") by vger.kernel.org with ESMTP id S964845AbWBMUEX (ORCPT ); Mon, 13 Feb 2006 15:04:23 -0500 Date: Mon, 13 Feb 2006 22:05:46 +0200 From: "Michael S. Tsirkin" To: Linus Torvalds Cc: Roland Dreier , Nick Piggin , Gleb Natapov , Benjamin Herrenschmidt , Linux Kernel Mailing List , openib-general@openib.org, Petr Vandrovec , Badari Pulavarty , Hugh Dickins Subject: Re: Re: madvise MADV_DONTFORK/MADV_DOFORK Message-ID: <20060213200546.GG12458@mellanox.co.il> Reply-To: "Michael S. Tsirkin" References: <20060213154114.GO32041@mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 13 Feb 2006 20:06:15.0156 (UTC) FILETIME=[F1A0E340:01C630D8] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 923 Lines: 21 Quoting Linus Torvalds : > I would suggest that if you wanted to be very careful, you'd simply > disallow changing - or perhaps just clearing - that DONTCOPY flag on > special regions (ie ones that have been marked with VM_IO or VM_RESERVED). Right, this was already proposed here http://lkml.org/lkml/2005/11/3/81 and I site: > You're then saying that a process cannot set VM_DONTCOPY on a VM_IO > area to prevent the first child getting the area, but clear it after > so the next child does get a copy of the area. I think it'd be wrong > (surprising) to limit the functionality in that way. -- Michael S. Tsirkin Staff Engineer, Mellanox Technologies - 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/