Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753469AbYAWXO2 (ORCPT ); Wed, 23 Jan 2008 18:14:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752258AbYAWXOS (ORCPT ); Wed, 23 Jan 2008 18:14:18 -0500 Received: from wa-out-1112.google.com ([209.85.146.182]:32457 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751724AbYAWXOR (ORCPT ); Wed, 23 Jan 2008 18:14:17 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YTAAWgqehRpu+K97RuDVorue4omOEpLq8Agkr7yMb+84hCKGr/lpSD3ZLfyGOQk5GTuv4anxXu91V4bC0De0bj/3dG13EAJxNqrcchr7XJvYPKVEFAKFqrpPXnhXuaY+EPgWfGcG0ya/UbS61pS9IDLu0OA8QlaTn3EZeHz1tXo= Message-ID: <4df4ef0c0801231514ga32b513g4917d715f9888ac6@mail.gmail.com> Date: Thu, 24 Jan 2008 02:14:16 +0300 From: "Anton Salikhmetov" To: "Linus Torvalds" Subject: Re: [PATCH -v8 2/4] Update ctime and mtime for memory-mapped files Cc: linux-mm@kvack.org, jakob@unthought.net, linux-kernel@vger.kernel.org, valdis.kletnieks@vt.edu, riel@redhat.com, ksm@42.dk, staubach@redhat.com, jesper.juhl@gmail.com, a.p.zijlstra@chello.nl, akpm@linux-foundation.org, protasnb@gmail.com, miklos@szeredi.hu, r.e.wolff@bitwizard.nl, hidave.darkstar@gmail.com, hch@infradead.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <12010440803930-git-send-email-salikhmetov@gmail.com> <12010440822957-git-send-email-salikhmetov@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1189 Lines: 32 2008/1/23, Linus Torvalds : > > > On Wed, 23 Jan 2008, Anton Salikhmetov wrote: > > > > Update ctime and mtime for memory-mapped files at a write access on > > a present, read-only PTE, as well as at a write on a non-present PTE. > > Ok, this one I'm applying. I agree that it leaves MS_ASYNC not updating > the file until the next sync actually happens, but I can't really bring > myself to care at least for an imminent 2.6.24 thing. The file times are > actually "correct" in the sense that they will now match when the IO is > done, and my man-page says that MS_ASYNC "schedules the io to be done". > > And I think this is better than we have now, and I don't think this part > is somethign that anybody really disagrees with. > > We can (and should) keep the MS_ASYNC issue open. Thank you! I have closed the bug #2645, because this patch solves the issue originally reported. > > Linus > -- 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/