Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Mar 2001 01:00:39 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Mar 2001 01:00:29 -0500 Received: from perninha.conectiva.com.br ([200.250.58.156]:34313 "HELO postfix.conectiva.com.br") by vger.kernel.org with SMTP id ; Tue, 20 Mar 2001 01:00:13 -0500 Date: Tue, 20 Mar 2001 01:15:20 -0300 (BRT) From: Marcelo Tosatti To: Linus Torvalds Cc: Rik van Riel , Mike Galbraith , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Manfred Spraul , MOLNAR Ingo Subject: Re: 3rd version of R/W mmap_sem patch available 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 On Mon, 19 Mar 2001, Linus Torvalds wrote: > > There is a 2.4.3-pre5 in the test-directory on ftp.kernel.org. > > The complete changelog is appended, but the biggest recent change is the > mmap_sem change, which I updated with new locking rules for pte/pmd_alloc > to avoid the race on the actual page table build. > > This has only been tested on i386 without PAE, and is known to break other > architectures. Ingo, mind checking what PAE needs? Generally, the changes > are simple, and really only implies changing the pte/pmd allocation > functions to _only_ allocate (ie removing the stuff that actually modifies > the page tables, as that is now handled by generic code), and to make sure > that the "pgd/pmd_populate()" functions do the right thing. > > I have also removed the xxx_kernel() functions - for architectures that > need them, I suspect that the right approach is to just make the > "populate" funtions notice when "mm" is "init_mm", the kernel context. > That removed a lot of duplicate code that had little good reason. > > This pre-release is meant mainly as a synchronization point for mm > developers, not for generic use. > > Thanks, > > Linus > > > ----- > -pre5: > - Rik van Riel and others: mm rw-semaphore (ps/top ok when swapping) > - IDE: 256 sectors at a time is legal, but apparently confuses some > drives. Max out at 255 sectors instead. Could the IDE one cause corruption ? EXT2-fs error (device ide0(3,1)): ext2_free_blocks: bit already cleared for block 6211 Just hitted this now with pre3. - 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/