From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rik van Riel Subject: Re: [PATCH] inotify: add hook to catch fsync/msync events Date: Mon, 30 Mar 2009 14:17:27 -0400 Message-ID: <49D10CB7.7020805@redhat.com> References: <1238434567.3597.31.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, john@johnmccutchan.com, rlove@rlove.org, Eric Paris , Jeff Layton To: Simo Sorce Return-path: Received: from mx2.redhat.com ([66.187.237.31]:34641 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756655AbZC3SRe (ORCPT ); Mon, 30 Mar 2009 14:17:34 -0400 In-Reply-To: <1238434567.3597.31.camel@localhost.localdomain> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Simo Sorce wrote: > An external application that is interested to know if a database file has > changed (in a meaningful way), would have no other way but to listen for > IN_SYNC events. Normal inotify tells the listener "something changed". IN_SYNC tells the listeners "there is new, useful data". Because this new inotify signal gives the listener more useful information than the existing inotify paths, at least for your use case, I believe the patch makes perfect sense and should be merged. > Signed-off-by: Simo Sorce Reviewed-by: Rik van Riel -- All rights reversed.