From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751346AbaJFULs (ORCPT ); Mon, 6 Oct 2014 16:11:48 -0400 Received: from mout.gmx.net ([212.227.17.20]:64275 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750720AbaJFULq (ORCPT ); Mon, 6 Oct 2014 16:11:46 -0400 Message-ID: <5432F6E8.7010607@gmx.de> Date: Mon, 06 Oct 2014 22:09:12 +0200 From: Heinrich Schuchardt User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.0 MIME-Version: 1.0 To: Jan Kara CC: Alexander Viro , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Eric Paris , Michael Kerrisk , John McCutchan , Robert Love Subject: Re: [PATCH 1/1] ftruncate: create FAN_MODIFY and IN_MODIFY events References: <1412360190-1507-1-git-send-email-xypron.glpk@gmx.de> <20141006132449.GD7526@quack.suse.cz> In-Reply-To: <20141006132449.GD7526@quack.suse.cz> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:0zmIQkYq9HYPV1MoCuukeJsLzpK8zzFLeRDEx9pVM85sI8MRbzm zzT4iN1Nnvrdi2jCexTk0kuYgihQQhCK/iJaL6MaM6nvaQ9D4Gs9Cdc0hz5iA50JVa5hFVv 2zqeEJyjOk9UaWqM+o0B2XTZvEHAJgdYFlJVEIOZtVNDYPiN3x0WcUYvNCgAirRATcJ5LNY IPjk7k3u439L2lM1BBmvQ== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06.10.2014 15:24, Jan Kara wrote: > On Fri 03-10-14 20:16:30, Heinrich Schuchardt wrote: >> The fanotify and the inotify API can be used to monitor changes of the file >> system. >> >> System call ftruncate modifies files. Hence it should trigger the corresponding >> fanotify (FAN_MODIFY) and inotify (IN_MODIFY) events. > Hum, I would think that the appropriate event gets generated by > fsnotify_change() called from notify_change()? > > Honza Hello Jan, thank you for reviewing. fsnotify_change() calls fsnotify(inode, mask, inode, FSNOTIFY_EVENT_INODE, NULL, 0); fsnotify_modify() calls fsnotify(inode, mask, path, FSNOTIFY_EVENT_PATH, NULL, 0); Only with FSNOTIFY_EVENT_PATH a mount is determined in fsnotify(). So a FAN_MODIFY event for a mount cannot occur. But I also did not see a FAN_MODIFY event when watching a file either. IN_MODIFY events are actually created. So would it be better to do the change in do_truncate and replace the call to notify_change by a call to fsnotify_modify? I just had a look at http://lxr.free-electrons.com/ident?i=notify_change There seem to be some other usages of notify_change that deserve consideration, e.g. in ecryptfs_truncate(). Best regards Heinrich Schuchardt >> >> Signed-off-by: Heinrich Schuchardt >> --- >> fs/open.c | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/fs/open.c b/fs/open.c >> index d6fd3ac..e36f26e 100644 >> --- a/fs/open.c >> +++ b/fs/open.c >> @@ -189,6 +189,8 @@ static long do_sys_ftruncate(unsigned int fd, loff_t length, int small) >> error = security_path_truncate(&f.file->f_path); >> if (!error) >> error = do_truncate(dentry, length, ATTR_MTIME|ATTR_CTIME, f.file); >> + if (!error) >> + fsnotify_modify(f.file); >> sb_end_write(inode->i_sb); >> out_putf: >> fdput(f); >> -- >> 2.1.0 >>