Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 12 Jun 2002 03:20:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 12 Jun 2002 03:20:38 -0400 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:29188 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Wed, 12 Jun 2002 03:20:37 -0400 Subject: Re: 2.4.18 no timestamp update on modified mmapped files To: hugh@veritas.com (Hugh Dickins) Date: Wed, 12 Jun 2002 08:40:54 +0100 (BST) Cc: akpm@zip.com.au (Andrew Morton), kaos@ocs.com.au (Keith Owens), linux-kernel@vger.kernel.org In-Reply-To: from "Hugh Dickins" at Jun 11, 2002 10:10:28 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > On Tue, 11 Jun 2002, Andrew Morton wrote: > > > > I think it's too late to fix this in 2.4. If we did, a person > > could develop and test an application on 2.4.21, ship it, then > > find that it fails on millions of 2.4.17 machines. > > Oh, please reconsider that! Doesn't loss of modification time > approach data loss? Surely we'll continue to fix any data loss > issues in 2.4, and be grateful if you fixed this mmap modtime loss. It doesnt approach data loss, when doing incremental backups it *is* data loss. Ditto with rsync --newer - 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/