Messages in this thread | | | Date | Thu, 22 Nov 2007 20:49:43 -0500 | From | "Morten Welinder" <> | Subject | Re: Inotify fails to send IN_ATTRIB events |
| |
> Wanna try the patch below?
With this patch I am seeing a endless stream of IN_IGNORED events for a removed watch. I don't see a reason that user space should ever see any IN_IGNORED, but an endless steam is not good.
Utterly unrelated, inotify does not work in /proc/. The list archives suggest that it isn't likely to start working anytime soon, but shouldn't inotify_add_watch when fail with ENOSYS instead of pretending it worked?
Morten
Failed to create inotify watch for /home/welinder/hi: No such file or directory Created inotify watch 1 with mask 0x000007c0 for /home/welinder # "touch hi" here Got event 00000100 for 1 Created inotify watch 2 with mask 0x00000fc6 for /home/welinder/hi Removing notify watch 1 Got event 00008000 for 1 Got event 00000004 for 2 # "rm hi" here Got event 00000400 for 2 Removing notify watch 2 Got event 00008000 for 2 Failed to create inotify watch for /home/welinder/hi: No such file or directory Created inotify watch 3 with mask 0x000007c0 for /home/welinder Got event 00000200 for 3 Failed to create inotify watch for /home/welinder/hi: No such file or directory Created inotify watch 3 with mask 0x000007c0 for /home/welinder # "touch hi" here Got event 00000100 for 3 Created inotify watch 4 with mask 0x00000fc6 for /home/welinder/hi Removing notify watch 3 Got event 00008000 for 3 Got event 00000004 for 4 Got event 00000004 for 4 # "rm hi" here Got event 00000400 for 4 Removing notify watch 4 Failed to create inotify watch for /home/welinder/hi: No such file or directory Created inotify watch 5 with mask 0x000007c0 for /home/welinder Got event 00008000 for 4 Got event 00008000 for 4 Got event 00008000 for 4 Got event 00008000 for 4 ... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |