From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Amy Griffis <amy.griffis@hp.com>
Cc: linux-kernel@vger.kernel.org,
John McCutchan <ttb@tentacle.dhs.org>,
Andrew Morton <akpm@osdl.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] inotify: IN_DELETE events missing in -mm
Date: Thu, 30 Mar 2006 12:51:19 +1100 [thread overview]
Message-ID: <442B3997.7020900@yahoo.com.au> (raw)
In-Reply-To: <20060329155719.GA22092@zk3.dec.com>
Amy Griffis wrote:
>In recent -mm kernels (e.g. 2.6.16-mm1), IN_DELETE events are no longer
>generated for the removal of a file from a watched directory.
>
>This seems to be a result of clearing DCACHE_INOTIFY_PARENT_WATCHED in
>d_delete() directly before calling fsnotify_nameremove().
>
>Assuming the flag doesn't need to be cleared before dentry_iput(), this should
>do the trick.
>
>
Thanks Amy. This should go to the next -stable kernel too.
>Signed-off-by: Amy Griffis <amy.griffis@hp.com>
>
>diff --git a/fs/dcache.c b/fs/dcache.c
>index 363cd4b..344ce91 100644
>--- a/fs/dcache.c
>+++ b/fs/dcache.c
>@@ -1198,11 +1198,11 @@ void d_delete(struct dentry * dentry)
> spin_lock(&dentry->d_lock);
> isdir = S_ISDIR(dentry->d_inode->i_mode);
> if (atomic_read(&dentry->d_count) == 1) {
>- /* remove this and other inotify debug checks after 2.6.18 */
>- dentry->d_flags &= ~DCACHE_INOTIFY_PARENT_WATCHED;
>-
> dentry_iput(dentry);
> fsnotify_nameremove(dentry, isdir);
>+
>+ /* remove this and other inotify debug checks after 2.6.18 */
>+ dentry->d_flags &= ~DCACHE_INOTIFY_PARENT_WATCHED;
> return;
> }
>
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-03-30 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 15:57 [PATCH] inotify: IN_DELETE events missing in -mm Amy Griffis
2006-03-29 21:37 ` John McCutchan
2006-03-29 21:37 ` John McCutchan
2006-03-30 1:51 ` Nick Piggin [this message]
2013-10-16 20:38 ` Jim Mostek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=442B3997.7020900@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=amy.griffis@hp.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ttb@tentacle.dhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.