From: Eric Paris <eparis@redhat.com>
To: Alexey Zaytsev <alexey.zaytsev@gmail.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
linux-fsdevel@vger.kernel.org,
"stefan@buettcher.org" <stefan@buettcher.org>,
linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: A possible flaw in the fsnotify design.
Date: Mon, 15 Nov 2010 17:11:18 -0500 [thread overview]
Message-ID: <1289859078.14282.28.camel@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimxbVnTVGobxhSTieJ4-PCTOZE_F6_E1-=8JcrO@mail.gmail.com>
On Tue, 2010-11-16 at 01:05 +0300, Alexey Zaytsev wrote:
> Just some thoughts.
>
> Consider the situation: Files A and B both point to the same inode.
> File A is being watched, but the user won't get notifications if B is
> modified.
That's not true. Users watch inodes, not files (this is true for both
inotify and fanotify). Give it a try, it works.
-Eric
next prev parent reply other threads:[~2010-11-15 22:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 22:05 A possible flaw in the fsnotify design Alexey Zaytsev
2010-11-15 22:11 ` Eric Paris [this message]
2010-11-15 22:44 ` Alexey Zaytsev
2010-11-15 22:51 ` Eric Paris
2010-11-15 23:03 ` Alexey Zaytsev
2010-11-15 23:12 ` Eric Paris
2010-11-15 23:15 ` Alexey Zaytsev
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=1289859078.14282.28.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=alexey.zaytsev@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@buettcher.org \
--cc=tvrtko.ursulin@sophos.com \
--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 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).