[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTimxbVnTVGobxhSTieJ4-PCTOZE_F6_E1-=8JcrO@mail.gmail.com>
Date: Tue, 16 Nov 2010 01:05:09 +0300
From: Alexey Zaytsev <alexey.zaytsev@...il.com>
To: Eric Paris <eparis@...hat.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@...hos.com>,
linux-fsdevel@...r.kernel.org,
"stefan@...ttcher.org" <stefan@...ttcher.org>,
linux-kernel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>
Subject: A possible flaw in the fsnotify design.
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.
This might be a problem for indexers, or, in my case, backup programs.
Even if the user is watching the mont point, he still needs to get all
the possible links to the modified file, and in my understanding,
there is no way to do this without scanning the whole filesystem.
I've got no idea how to fix the problem yet, or if it would be
possible to fix at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists