From: Al Viro <viro@ZenIV.linux.org.uk>
To: Steve French <smfrench@gmail.com>
Cc: Jamie Lokier <jamie@shareable.org>,
Jeff Layton <jlayton@redhat.com>,
linux-cifs-client@lists.samba.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] cifs: remove dnotify thread code
Date: Fri, 9 Jan 2009 18:18:56 +0000 [thread overview]
Message-ID: <20090109181855.GX28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <524f69650901081932m2912ab73x147221f721194f8@mail.gmail.com>
On Thu, Jan 08, 2009 at 09:32:09PM -0600, Steve French wrote:
> What worries me most about losing the ability to add directory change
> notification in the future (without putting the entry point back) the
If you put that one entry point back, please make sure to reserve a CVE number
first.
> lack of directory change notification is quite visible to the user
> when an open directory object on the desktop (gnome or kde) does not
> automatically refresh within a few seconds as files are added on the
> remote system (or on another client).
>
> The old cifs implementation was broken (partially implemented) but it
> was "dead code" so was harmless (it required configuring with
> CONFIG_CIFS_EXPERIMENTAL and turning on a run time flag in
> /proc/fs/cifs to enable it) but it might not have been too bad to
> finish the implementation.
The interface for it had been inherently broken. Whatever you do with the
cifs side, you'd have to change the VFS side. Might as well start from scratch.
Again, *any* experimenting with that crap will have to start with figuring
out what to do with destruction of these suckers.
prev parent reply other threads:[~2009-01-09 18:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 14:15 [PATCH] cifs: remove dnotify thread code Jeff Layton
2009-01-08 14:23 ` Steve French
2009-01-08 14:51 ` Jeff Layton
2009-01-09 0:07 ` Jamie Lokier
2009-01-09 1:28 ` Jeff Layton
2009-01-10 1:35 ` Jamie Lokier
2009-01-10 1:41 ` Jamie Lokier
2009-01-10 18:19 ` Steve French
2009-01-09 3:32 ` Steve French
2009-01-09 11:33 ` Jeff Layton
2009-01-09 16:18 ` Steve French
2009-01-09 18:07 ` Jeff Layton
2009-01-09 18:18 ` Al Viro [this message]
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=20090109181855.GX28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=jamie@shareable.org \
--cc=jlayton@redhat.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=smfrench@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).