From: "Morten Welinder" <mwelinder@gmail.com>
To: "Jan Kara" <jack@suse.cz>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
rlove@rlove.org, "Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: Inotify fails to send IN_ATTRIB events
Date: Thu, 22 Nov 2007 20:49:43 -0500 [thread overview]
Message-ID: <118833cc0711221749h2da36d7ek856ee91cdeda955@mail.gmail.com> (raw)
In-Reply-To: <20071122153446.GA6299@atrey.karlin.mff.cuni.cz>
> 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
...
next prev parent reply other threads:[~2007-11-23 1:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 3:11 Morten Welinder
2007-11-22 15:34 ` Jan Kara
2007-11-23 1:49 ` Morten Welinder [this message]
2007-11-23 14:18 ` Morten Welinder
2007-11-23 19:54 ` Morten Welinder
2007-11-26 16:00 ` Jan Kara
[not found] ` <118833cc0711260806x69fc2bb6n572f1e1253a201ef@mail.gmail.com>
2007-11-26 16:27 ` [PATCH] Send IN_ATTRIB events when link count changes Jan Kara
2007-11-27 20:46 ` Andrew Morton
2007-11-28 12:53 ` Jan Kara
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=118833cc0711221749h2da36d7ek856ee91cdeda955@mail.gmail.com \
--to=mwelinder@gmail.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®