Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262659AbUKEMLr (ORCPT ); Fri, 5 Nov 2004 07:11:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262660AbUKEMLr (ORCPT ); Fri, 5 Nov 2004 07:11:47 -0500 Received: from mx1.redhat.com ([66.187.233.31]:27800 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S262659AbUKEMLq (ORCPT ); Fri, 5 Nov 2004 07:11:46 -0500 From: David Howells In-Reply-To: <418B0C82.6060107@snapgear.com> References: <418B0C82.6060107@snapgear.com> <19972.1099578526@redhat.com> To: uClinux development list Cc: linux-kernel@vger.kernel.org Subject: Re: [uClinux-dev] bug in order>0 page allocations with !CONFIG_MMU User-Agent: EMH/1.14.1 SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Date: Fri, 05 Nov 2004 12:11:39 +0000 Message-ID: <23098.1099656699@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 771 Lines: 19 > > Why is doing this necessary at all? No one should be touching the > > individual pages of a block allocation. The kernel should defend itself > > against userspace trying to munmap part of a multipage mmap. > > I don't recall right now why we had to do this originally. > It was absolutely neccessary once, but I don't think we need > this anymore. At least it runs fine on m68knommu targets now > without this. I've just found out what it's necessary for. access_process_vm() as called from, say, /proc/cmdline. David - 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/