Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262501AbVA0AZy (ORCPT ); Wed, 26 Jan 2005 19:25:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262495AbVA0AYb (ORCPT ); Wed, 26 Jan 2005 19:24:31 -0500 Received: from quark.didntduck.org ([69.55.226.66]:49802 "EHLO quark.didntduck.org") by vger.kernel.org with ESMTP id S262512AbVAZXbX (ORCPT ); Wed, 26 Jan 2005 18:31:23 -0500 Message-ID: <41F82844.7020504@didntduck.org> Date: Wed, 26 Jan 2005 18:31:16 -0500 From: Brian Gerst User-Agent: Mozilla Thunderbird (X11/20041216) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-os@analogic.com CC: Rik van Riel , Andrew Morton , linux-kernel@vger.kernel.org, James Antill , Bryn Reeves Subject: Re: don't let mmap allocate down to zero References: In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 936 Lines: 26 linux-os wrote: > On Wed, 26 Jan 2005, Rik van Riel wrote: > >> With some programs the 2.6 kernel can end up allocating memory >> at address zero, for a non-MAP_FIXED mmap call! This causes >> problems with some programs and is generally rude to do. This >> simple patch fixes the problem in my tests. > > > Does this mean that we can't mmap the screen regen buffer at > 0x000b8000 anymore? > > How do I look at the real-mode interrupt table starting at > offset 0? You know that the return value of mmap is to be > checked for MAP_FAILED, not for NULL, don't you? This does not affect the case where the user requests a specific virrtual address (ie. vm86 stuff). -- Brian Gerst - 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/