From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH] VFS/inotify: send netlink messages when an inotify watch has been set or removed. Date: Sat, 7 Jan 2012 15:57:07 +0000 Message-ID: <20120107155707.GO23916@ZenIV.linux.org.uk> References: <4F084A4C.6080207@bononline.nl> <20120107143802.GM23916@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stef Bon , linux-fsdevel@vger.kernel.org, rlove@rlove.org, eparis@parisplace.org To: Stef Bon Return-path: Received: from zeniv.linux.org.uk ([195.92.253.2]:39692 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751548Ab2AGP5J (ORCPT ); Sat, 7 Jan 2012 10:57:09 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sat, Jan 07, 2012 at 04:03:26PM +0100, Stef Bon wrote: > Futher, the FUSE fs knows it's own mountpoint. (ignore the submounts > on a FUSE fs here), it can filter out the watches which are set on the > fs. BTW, how does FUSE fs know its mountpoint? Other than "my fs won't be mounted other than and if you mount it elsewhere, it's your problem" I don't see any possible way to do that... Note that no information about the intended mountpoint reaches fuse_mount() (and it would've been useless there anyway, since mountpoint can change at literally zero notice, so the userland side of FUSE would have no use for it), which leaves only the apriori knowledge ("my code assumes that it'll be mounted here, violate that assumption at your peril")...