Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754285AbYAPKMS (ORCPT ); Wed, 16 Jan 2008 05:12:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752099AbYAPKMG (ORCPT ); Wed, 16 Jan 2008 05:12:06 -0500 Received: from fxip-0047f.externet.hu ([88.209.222.127]:42431 "EHLO pomaz-ex.szeredi.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752028AbYAPKMF (ORCPT ); Wed, 16 Jan 2008 05:12:05 -0500 To: hidave.darkstar@gmail.com CC: R.E.Wolff@bitwizard.nl, linux-kernel@vger.kernel.org, salikhmetov@gmail.com In-reply-to: (hidave.darkstar@gmail.com) Subject: Re: mtime updates for mmapped files. References: <20080116094640.GA2071@bitwizard.nl> Message-Id: From: Miklos Szeredi Date: Wed, 16 Jan 2008 11:11:58 +0100 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1010 Lines: 29 > > > > Hi, > > > > I wrote a small app yesterday that updates a file by mmapping the > > file (RW), changing the thing around, and then exiting. > > > > This did not trigger a change in the mtime of the file. Thus rsync > > didn't pick up that the file had changed. > > > > I understand that tracking every change to a RW mmapped file is > > costly, and thus unfeasable, but shouldn't then the close cause a > > mtime update? > > > > The server where this happened is running 2.6.21, so my apologies if > > this has already been corrected. > > This is an old bug, don't know if it was fixed or not. Please see > http://lkml.org/lkml/2006/5/17/138 It's not fixed yet, but Anton Salikhmetov is currently working on it: http://lkml.org/lkml/2008/1/15/202 Miklos -- 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/