Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 24 Oct 2002 15:08:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 24 Oct 2002 15:08:13 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:14481 "EHLO perninha.conectiva.com.br") by vger.kernel.org with ESMTP id ; Thu, 24 Oct 2002 15:08:12 -0400 Date: Thu, 24 Oct 2002 17:14:14 -0200 (BRST) From: Rik van Riel X-X-Sender: riel@duckman.distro.conectiva To: Andrea Arcangeli Cc: chrisl@vmware.com, Andrew Morton , , Subject: Re: writepage return value check in vmscan.c In-Reply-To: <20021024184005.GT3354@dualathlon.random> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org 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 Content-Length: 976 Lines: 26 On Thu, 24 Oct 2002, Andrea Arcangeli wrote: > unfortunately I see no way around it and patching the kernel to loop > forever on dirty pages that may never be possible to write doesn't look > safe. You could check the free space on the fs and bug the user if it > has less than 2G free (still it's not 100% reliable, it's a racy check, > but you could also add a 100% reliable option that slowdown the startup > of the vm but that guarantees no corruption can happen). We need space allocation. Not just for this (probably rare) case, but also for the more generic optimisation of delayed allocation. cheers, Rik -- A: No. Q: Should I include quotations after my reply? http://www.surriel.com/ http://distro.conectiva.com/ - 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/