From: Robert Love <rml@novell.com>
To: Steve French <smfltc@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: supporting functions missing from inotify patch
Date: Wed, 13 Jul 2005 15:12:42 -0400 [thread overview]
Message-ID: <1121281962.6384.36.camel@betsy> (raw)
In-Reply-To: <1121280212.5544.46.camel@stevef95.austin.ibm.com>
On Wed, 2005-07-13 at 13:43 -0500, Steve French wrote:
> I don't see an inode operation for registering inotify events in the fs
> (there is a file operation for dir_notify to register its events). In
> create_watch in fs/inotify.c I expected to see something like:
Why not use the existing dir_notify method? No point in adding another.
Add inotify hooks as needed to your filesystem's dir_notify.
> I also don't see exports for
> fsnotify_access
> fsnotify_modify
>
> Without these exports, network and cluster filesystems can't notify the
> local system about changes.
Eh?
They are in <linux/fsnotify.h>.
Robert Love
next prev parent reply other threads:[~2005-07-13 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 18:43 supporting functions missing from inotify patch Steve French
2005-07-13 19:12 ` Robert Love [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-13 20:21 Steve French
2005-07-13 20:39 ` Robert Love
2005-07-13 21:51 ` Steve French
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=1121281962.6384.36.camel@betsy \
--to=rml@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=smfltc@us.ibm.com \
/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.