From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: Sylvain Rochet <gradator@gradator.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org
Subject: Re: PROBLEM: 2.6.35.7 to 3.0 Inotify events missing
Date: Sat, 20 Aug 2011 02:29:43 +0100 [thread overview]
Message-ID: <20110820012943.GD2203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20110819233756.GI11512@jl-vm1.vm.bytemark.co.uk>
On Sat, Aug 20, 2011 at 12:37:56AM +0100, Jamie Lokier wrote:
> Possible solution:
> Then this can be solved, in principle (if there's no better way), by
> watching a "virtual directory" that gets all events for when the
> access doesn't have a parent directory. There needs to be some way to
> watch it, and some way to get the appropriate file from the event (as
> there is no real directory. Or maybe there could be a virtual
> filesystem (like /proc, /sys etc.) containing a magic directory that
> receives these inode-only events, such that lookups in that directory
> yield the affected file. Exactly as if the directory contains a hard
> link to every file, perhaps a text encoding of the handles passed
> through sys_open_by_handle_at.
There is a better way - stop using idiotify... It has always been a
mistake, driven down our throats by filemangler and desktop crowd.
Broken in many, _many_ respects... Deprecate that crap, remove it
completely in a couple of revisions, let these clowns cope. Yeah,
yeah, I know... Not going to happen ;-/ One can dream, though...
next prev parent reply other threads:[~2011-08-20 1:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 22:35 PROBLEM: 2.6.35.7 Inotify events missing Sylvain Rochet
2011-08-19 23:03 ` PROBLEM: 2.6.35.7 to 3.0 " Sylvain Rochet
2011-08-19 23:37 ` Jamie Lokier
2011-08-19 23:37 ` Jamie Lokier
2011-08-20 0:47 ` Sylvain Rochet
2011-08-20 0:47 ` Sylvain Rochet
2011-08-20 3:21 ` Jamie Lokier
2011-08-20 1:29 ` Al Viro [this message]
2011-08-20 1:43 ` Randy Dunlap
2011-08-20 2:01 ` Al Viro
2011-08-20 3:03 ` Jamie Lokier
2011-08-20 3:03 ` Jamie Lokier
2011-08-21 17:07 ` J. Bruce Fields
2011-08-21 17:07 ` J. Bruce Fields
2011-08-21 20:20 ` Jamie Lokier
2011-08-21 20:20 ` Jamie Lokier
2011-08-21 23:07 ` NeilBrown
2011-08-22 17:22 ` J. Bruce Fields
2011-08-22 23:21 ` NeilBrown
2011-08-22 23:21 ` NeilBrown
2011-08-25 21:47 ` Sylvain Rochet
2011-08-21 22:29 ` NeilBrown
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=20110820012943.GD2203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=gradator@gradator.net \
--cc=jamie@shareable.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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.