Re: [patch] stop inotify from sending random DELETE_SELF event under load

On Mon, Sep 19, 2005 at 10:00:41PM -0400, John McCutchan wrote:
> To quote you:
> 
> Instead of the broken fsnotify_unlink/fsnotify_rmdir functions, you can 
> split this into two logically _different_ functions:
> 
>  - fsnotify_nameremove(dentry) - called when the dentry goes away
>  - fsnotify_inoderemove(dentry) - called when the inode goes away
> 
> ...
> 
> The fsnotify_inoderemove() is called from dentry_iput(), and that's the 
> one that specifies that an actual inode no longer exists.
> 
> 
> ;)

That was wrong.  Just have *one* function (on link removal) and stuff
i_mode and i_nlink of victim into event.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch] stop inotify from sending random DELETE_SELF event under load
    • From: John McCutchan <[email protected]>

• References:
  • [patch] stop inotify from sending random DELETE_SELF event under load
    • From: John McCutchan <[email protected]>
  • Re: [patch] stop inotify from sending random DELETE_SELF event under load
    • From: Linus Torvalds <[email protected]>
  • Re: [patch] stop inotify from sending random DELETE_SELF event under load
    • From: John McCutchan <[email protected]>

• Prev by Date: Re: I request inclusion of reiser4 in the mainline kernel
• Next by Date: Re: Arrr! Linux v2.6.14-rc2
• Previous by thread: Re: [patch] stop inotify from sending random DELETE_SELF event under load
• Next by thread: Re: [patch] stop inotify from sending random DELETE_SELF event under load
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]