Re: [patch] stop inotify from sending random DELETE_SELF event underload
From: Linus Torvalds
Date: Tue Sep 20 2005 - 14:37:56 EST
On Tue, 20 Sep 2005, Al Viro wrote:
> >
> > I really think that the patch I sent out yesterday is as good as it gets.
> > If you want immediate notification, you should ask for notification about
> > name changes in a particular directory. IN_DELETE_SELF notification on a
> > file simple is _not_ going to be immediate.
>
> But then it's too early. Note that with your patch we still get removal
> of _any_ link to our inode (even though it's alive and well and we'd never
> heard about the sodding link in the first place) terminating all events
> on it.
Yes. What is in the current 2.6.14-rc2 tree doesn't do that. It considers
inodes "global". But it won't work reliably on networked filesystems, I
think.
Anyway, I do believe that IN_DELETE_SELF is stupid, but that you migth
re-arm it if you get it.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/