[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201008192307.32526.agruen@suse.de>
Date: Thu, 19 Aug 2010 23:07:31 +0200
From: Andreas Gruenbacher <agruen@...e.de>
To: Eric Paris <eparis@...hat.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Matt Helsley <matthltc@...ibm.com>,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
Michael Kerrisk <michael.kerrisk@...il.com>
Subject: Re: [GIT PULL] notification tree - try 37!
On Thursday 19 August 2010 22:42:45 Eric Paris wrote:
> The extra events are plainly the new events that inotify doesn't
> support: namely permissions events. You ask for and received extra
> events....
How can it make sense that inotify suddenly starts seeing events it does not
support?
> I can't reproduce it. You must have some other testing methodology.....
Apparently. Here is a trace if what I'm getting through inotify (the inotify
events were dumped with gdb, the rest is from strace):
inotify_init() = 3
inotify_add_watch(3, "d", IN_ACCESS|IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_CLOSE_NOWRITE|IN_OPEN|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|
IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF) = 1
read(3, "\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0 \0\0@\0\0\0\0\0\0\0\0", 4210688) = 32
=> {wd = 1, mask = 0, cookie = 0, len = 0, name = ...}
=> {wd = 1, mask = 1073741856, cookie = 0, len = 0, name = ...}
read(3, "\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\20\0\0@\0\0\0\0\0\0\0\0", 4210688) = 32
=> {wd = 1, mask = 0, cookie = 0, len = 0, name = ...}
=> {wd = 1, mask = 1073741840, cookie = 0, len = 0, name = ...}
read(3, 0x7fff56db15e0, 4210688) = -1 EINTR (Interrupted system call)
Andreas
--
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