Re: [PATCH -v3 8/8] dnotify: reimplement dnotify using fsnotify

[Al Viro]

On Tue, Nov 25, 2008 at 12:21:33PM -0500, Eric Paris wrote:
> -	inode->i_dnotify_mask |= arg & ~DN_MULTISHOT;
> -	dn->dn_next = inode->i_dnotify;
> -	inode->i_dnotify = dn;
> -	spin_unlock(&inode->i_lock);
> -
> -	if (filp->f_op && filp->f_op->dir_notify)
> -		return filp->f_op->dir_notify(filp, arg);
> +	dn->dn_next = entry->private;
> +	entry->private = dn;
> +	dnotify_recalc_inode_mask(entry);
> +	spin_unlock(&inode->i_fsnotify_lock);
> +	fsnotify_mark_put(entry);
> +	fsnotify_put_group(dnotify_group);

Now, that is interesting - you've just taken out the fscked-in-head
->dir_notify().  The action is quite laudable, but it deserves being
announced properly:

* Remove the hopelessly misguided ->dir_notify().  The only instance (cifs)
has been broken by design from the very beginning; the objects it creates
are never destroyed, keep references to struct file they can outlive, nothing
that could possibly evict them exists on close(2) path *and* no locking
whatsoever is done to prevent races with close(), should the previous, er,
deficiencies someday be dealt with.

While we are at it, removing the only call of that method is obviously
only a half of the job...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/