From: Maxim Uvarov <maxim.uvarov@oracle.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-nfs@vger.kernel.org, bfields@fieldses.org,
Trond.Myklebust@netapp.com, john@johnmccutchan.com,
rlove@rlove.org, eparis@parisplace.org
Subject: Re: [PATCH] NFS/INOTIFY: inotify user when deleting files on nfs
Date: Thu, 15 Dec 2011 11:12:30 -0800 [thread overview]
Message-ID: <4EEA469E.6070307@oracle.com> (raw)
In-Reply-To: <20111214232254.GP2203@ZenIV.linux.org.uk>
On 12/14/2011 03:22 PM, Al Viro wrote:
> On Wed, Dec 14, 2011 at 02:58:15PM -0800, Maxim Uvarov wrote:
>> This issue was introduced with LTP inotify02 test.
>> If file system is not NFS user inotify application
>> gets IN_DELETE event. But on NFS code avoids d_delete()
>> which sends this event. This patch makes notification
>> on NFS the same as non-NFS. I.e. vfs_unlink still avoids
>> deletion but it sends event for NFS sillyrenamed files.
>> More details here:
>> https://lkml.org/lkml/2011/11/29/421
>
> NAK. Too damn ugly. And completely misses the point of inotify -
> seeing events generated only by this client is going to be worthless.
> Face it, inotify is broken by design for network filesystems. Any
> software using it on NFS is broken; trying to paper over that is
> not a good idea.
>
> Just. Don't. Use. That. Shit.
Thank you for so technical answer. It's really difficult to object
against such considered and well-grounded, forcible arguments.
Now to be serious:
1. Original VFS code already has "if NFS", in vfs_unlink(). Because of
code does not call d_delete() it has to call notification from d_delete().
2. inotify is done on VFS layer. So logically it has to work on all file
systems.
3. We think that software works if it's execution matches specification.
Because we don't have any specification for inotify we can relay on
tests. I.e. if all test for all notification events passed the same way
for all file systems; events, number of events and sequence for events
matches and do not depend on file system type - we can say that this
feature works. As the base for inotify we can take LTP tests, which have
good coverage for all events.
Best regards,
Maxim Uvarov.
next prev parent reply other threads:[~2011-12-15 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 22:58 [PATCH] NFS/INOTIFY: inotify user when deleting files on nfs Maxim Uvarov
2011-12-14 22:58 ` Maxim Uvarov
2011-12-14 23:22 ` Al Viro
2011-12-15 19:12 ` Maxim Uvarov [this message]
2011-12-15 21:32 ` Al Viro
2011-12-15 21:52 ` Myklebust, Trond
2011-12-15 22:34 ` Maxim Uvarov
2011-12-15 22:58 ` Myklebust, Trond
2011-12-15 23:27 ` Maxim Uvarov
2011-12-16 20:50 ` Stef Bon
-- strict thread matches above, loose matches on Subject: below --
2011-12-14 22:27 Maxim Uvarov
2011-12-15 10:42 ` Boaz Harrosh
2011-12-15 10:42 ` Boaz Harrosh
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=4EEA469E.6070307@oracle.com \
--to=maxim.uvarov@oracle.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=eparis@parisplace.org \
--cc=john@johnmccutchan.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=viro@ZenIV.linux.org.uk \
/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.