Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 24 Jan 2003 14:59:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 24 Jan 2003 14:59:28 -0500 Received: from comtv.ru ([217.10.32.4]:27372 "EHLO comtv.ru") by vger.kernel.org with ESMTP id ; Fri, 24 Jan 2003 14:59:25 -0500 X-Comment-To: Andrew Morton To: Andrew Morton Cc: Alex Tomas , linux-kernel@alex.org.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: 2.5.59-mm5 References: <20030123195044.47c51d39.akpm@digeo.com> <946253340.1043406208@[192.168.100.5]> <20030124031632.7e28055f.akpm@digeo.com> <20030124035017.6276002f.akpm@digeo.com> <20030124111249.227a40d6.akpm@digeo.com> From: Alex Tomas Organization: HOME Date: 24 Jan 2003 22:58:13 +0300 In-Reply-To: <20030124111249.227a40d6.akpm@digeo.com> Message-ID: Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 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 >>>>> Andrew Morton (AM) writes: AM> We cannot free disk blocks until I/O against them has completed. AM> Otherwise the block could be reused for something else, then the AM> old IO will scribble on the new data. AM> What we _can_ do is to defer the waiting - only wait on the I/O AM> when someone reuses the disk blocks. So there are actually AM> unused blocks with I/O in flight against them. AM> We do that for metadata (the wait happens in AM> unmap_underlying_metadata()) but for file data blocks there is no AM> mechanism in place to look them up yeah! indeed. my stupid mistake ... - 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/