From: "Asser Femø" <asser@diku.dk>
To: linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: dnotify/inotify and vfs questions
Date: Tue, 23 Aug 2005 15:00:23 +0200 [thread overview]
Message-ID: <20050823130023.GB8305@diku.dk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
Hi,
I'm currently implementing change notification support for the linux
cifs client as part of Google's Summer of Code program.
In cifs, change notification works pretty much the same as dnotify does
in the kernel, and you cancel the notification by sending a NT_CANCEL
request.
According to the fcntl manual you can cancel a notification by doing
fcntl(fd, F_NOTIFY, 0) (ie. sending 0 as the notification mask), but
looking in the kernel code fcntl_dirnotify() immediately calls
dnotify_flush() with neither telling the vfs module about it. Is there a
reason for this? Otherwise I'd propose calling
filp->f_op->dir_notify(filp, 0) at some point in this scenario.
Regarding inotify, inotify_add_watch doesn't seem to pass on the request
either, which works fine for local filesystem operations as they call
fsnotify_* functions every time, but that isn't really feasible for
filesystems like cifs because we'd have to request change notification
on everything. Is there plans for implementing a mechanism to let vfs
modules get watch requests too?
cheers,
Asser
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-08-23 13:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 13:00 Asser Femø [this message]
2005-08-23 15:23 ` dnotify/inotify and vfs questions Jamie Lokier
2005-08-23 15:23 ` Jamie Lokier
2005-08-25 12:40 ` Ian Campbell
2005-08-25 14:57 ` Jamie Lokier
2005-08-25 15:07 ` Ian Campbell
2005-08-25 15:07 ` Ian Campbell
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=20050823130023.GB8305@diku.dk \
--to=asser@diku.dk \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.