All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Stef Bon <stef@bononline.nl>
Cc: linux-fsdevel@vger.kernel.org, rlove@rlove.org, eparis@parisplace.org
Subject: Re: [PATCH] VFS/inotify: send netlink messages when an inotify watch has been set or removed.
Date: Sat, 7 Jan 2012 14:38:02 +0000	[thread overview]
Message-ID: <20120107143802.GM23916@ZenIV.linux.org.uk> (raw)
In-Reply-To: <4F084A4C.6080207@bononline.nl>

On Sat, Jan 07, 2012 at 02:36:12PM +0100, Stef Bon wrote:
> from: Stef Bon
> 
> I would like to apply a patch to the kernel to enable the sending of a
> netlink message when setting or removing an inotify watch. My goal is
> to make FUSE filesystems notify aware.
> 
> Since inotify works in the kernel space, and FUSE filesystems are in
> userspace, FUSE fs's do not "know" when a watch has been set or
> removed.
> 
> I think it's a good thing the fs "knows" about a watch, since it can
> then set a backend specific notify watch on the backend, and report
> anything back to the kernel when something changes.
> 
> The new netlink.c file is almost a copy of the netlink.c file in
> fs/quota.
> 
> I've got a testprogram which receives messages in the group
> GENERIC/VFS_INOTIFY.
> If you want to test please email me. It just gives the information a
> watch has been set (by who, and where, which mask) and when removed
> (pid/fd/wd).

And what, pray tell, is the recepient to do with the contents of that
packet?  Pardon the bluntness, but how the hell is your FUSE fs
supposed to tell that pathname has anything to do with it, nevermind
telling which object would it relate to?  Especially when it has
no way to tell at which locations the damn thing happens to be mounted
from the caller POV.

NAK.

  reply	other threads:[~2012-01-07 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07 13:36 [PATCH] VFS/inotify: send netlink messages when an inotify watch has been set or removed Stef Bon
2012-01-07 14:38 ` Al Viro [this message]
2012-01-07 15:03   ` Stef Bon
2012-01-07 15:42     ` Al Viro
2012-01-07 15:57     ` Al Viro
2012-01-07 16:59       ` Stef Bon
2012-01-07 19:05         ` Al Viro
2012-01-07 21:13           ` Stef Bon
  -- strict thread matches above, loose matches on Subject: below --
2012-01-05 20:56 Stef Bon
2012-01-06 14:13 ` Stef Bon

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=20120107143802.GM23916@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=eparis@parisplace.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rlove@rlove.org \
    --cc=stef@bononline.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.