Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Nov 2002 07:45:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Nov 2002 07:45:51 -0500 Received: from pc1-cwma1-5-cust42.swa.cable.ntl.com ([80.5.120.42]:30643 "EHLO irongate.swansea.linux.org.uk") by vger.kernel.org with ESMTP id ; Mon, 18 Nov 2002 07:45:50 -0500 Subject: Re: [patch] threading fix, tid-2.5.47-A3 From: Alan Cox To: Ingo Molnar Cc: Luca Barbieri , Ulrich Drepper , Linus Torvalds , Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 18 Nov 2002 13:20:19 +0000 Message-Id: <1037625619.7547.6.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 807 Lines: 19 On Mon, 2002-11-18 at 12:26, Ingo Molnar wrote: > > and we have VM_DONTCOPY already, which is used by the DRM code. So it > would only be a question of exporting this API to userspace. The attached > patch adds MAP_DONTCOPY. I made it unpriviledged, i doubt it has any > security impact. What is the behaviour of someone setting VM_DONTCOPY on memory that was copy on write between a large number of processes (say an executable image) ? Don't copy - but don't copy from what, from the original mapping or from the COW mapping of the original mapping ? Alan - 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/