From: Robert Love <rml@novell.com>
To: John McCutchan <ttb@tentacle.dhs.org>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [RFC][PATCH] inotify 0.13
Date: Wed, 06 Oct 2004 16:51:52 -0400 [thread overview]
Message-ID: <1097095913.4160.13.camel@betsy.boston.ximian.com> (raw)
In-Reply-To: <1097095286.9199.2.camel@vertex>
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
On Wed, 2004-10-06 at 16:41 -0400, John McCutchan wrote:
> -add CLOSE_WRITE/CLOSE_NOWRITE events (rml)
> -CLOSE_* events are delivered in all circumstances now (rml)
The __fput() related bits here got dropped.
Attached, against 0.13.
Robert Love
[-- Attachment #2: inotify-0.13-rml-missing-fput-bits-1.patch --]
[-- Type: text/x-patch, Size: 1029 bytes --]
add make missing __fput() logic.
Signed-Off-By: Robert Love <rml@novell.com>
fs/file_table.c | 7 +++++++
1 files changed, 7 insertions(+)
diff -urN linux-inotify-0.13/fs/file_table.c linux/fs/file_table.c
--- linux-inotify-0.13/fs/file_table.c 2004-10-06 16:47:28.785451776 -0400
+++ linux/fs/file_table.c 2004-10-06 16:49:01.200402568 -0400
@@ -16,6 +16,7 @@
#include <linux/eventpoll.h>
#include <linux/mount.h>
#include <linux/cdev.h>
+#include <linux/inotify.h>
/* sysctl tunables... */
struct files_stat_struct files_stat = {
@@ -122,8 +123,14 @@
struct dentry *dentry = file->f_dentry;
struct vfsmount *mnt = file->f_vfsmnt;
struct inode *inode = dentry->d_inode;
+ u32 mask;
might_sleep();
+
+ mask = (file->f_mode & FMODE_WRITE) ? IN_CLOSE_WRITE : IN_CLOSE_NOWRITE;
+ inotify_dentry_parent_queue_event(dentry, mask, 0, dentry->d_name.name);
+ inotify_inode_queue_event(inode, mask, 0, NULL);
+
/*
* The function eventpoll_release() should be the first called
* in the file cleanup chain.
next prev parent reply other threads:[~2004-10-06 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 20:41 John McCutchan
2004-10-06 20:51 ` Robert Love [this message]
2004-10-06 20:55 ` Robert Love
2004-10-06 22:24 ` Robert Love
2004-10-06 23:03 ` Robert Love
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=1097095913.4160.13.camel@betsy.boston.ximian.com \
--to=rml@novell.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®