> This looks bad, though:
>
> include/linux/fsnotify.h:121: warning: passing argument 2 of
> 'audit_inode_child' from incompatible pointer type
>
> Missing "->d_inode"?
That's the difference between 2.6.22 and 2.6.24-git against which I
wrote the patch :).
This looks bad, though:
include/linux/fsnotify.h:121: warning: passing argument 2 of
'audit_inode_child' from incompatible pointer type
Missing -d_inode?
That's the difference between 2.6.22 and 2.6.24-git against which I
wrote the patch :).
This looks bad, though:
include/linux/fsnotify.h:121: warning: passing argument 2 of
'audit_inode_child' from incompatible pointer type
Missing "->d_inode"?
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
> With this patch I am seeing a endless stream of IN_IGNORED events
> for a removed watch.
Sorry, that problem was on the chair. side of the keyboard -- too much
turkey, I fear. It just happened to be easier to trigger with the patch's
double event on deletion.
I'd still love to see ENOSYS when
This looks bad, though:
include/linux/fsnotify.h:121: warning: passing argument 2 of
'audit_inode_child' from incompatible pointer type
Missing -d_inode?
M.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
With this patch I am seeing a endless stream of IN_IGNORED events
for a removed watch.
Sorry, that problem was on the chair. side of the keyboard -- too much
turkey, I fear. It just happened to be easier to trigger with the patch's
double event on deletion.
I'd still love to see ENOSYS when
> 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
Hi,
> I am seeing missing inotify IN_ATTRIB events in the following situation:
>
> 1. "touch foo"
>
> 2. Make inotify watch "foo"
>
> 3. "ln foo bar"
>--> Link count changed so I should have gotten an IN_ATTRIB.
>
> 4. "rm foo"
>--> Link count changed so I should have gotten an
Hi,
I am seeing missing inotify IN_ATTRIB events in the following situation:
1. touch foo
2. Make inotify watch foo
3. ln foo bar
-- Link count changed so I should have gotten an IN_ATTRIB.
4. rm foo
-- Link count changed so I should have gotten an IN_ATTRIB. (Or
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
I am seeing missing inotify IN_ATTRIB events in the following situation:
1. "touch foo"
2. Make inotify watch "foo"
3. "ln foo bar"
--> Link count changed so I should have gotten an IN_ATTRIB.
4. "rm foo"
--> Link count changed so I should have gotten an IN_ATTRIB. (Or
IN_DELETE_SELF;
I am seeing missing inotify IN_ATTRIB events in the following situation:
1. touch foo
2. Make inotify watch foo
3. ln foo bar
-- Link count changed so I should have gotten an IN_ATTRIB.
4. rm foo
-- Link count changed so I should have gotten an IN_ATTRIB. (Or
IN_DELETE_SELF;
I don't
12 matches
Mail list logo
