From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Date: Wed, 29 May 2019 11:16:27 +0000 Subject: Re: [PATCH 3/7] vfs: Add a mount-notification facility Message-Id: <15839.1559128587@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <155905930702.7587.7100265859075976147.stgit@warthog.procyon.org.uk> <155905933492.7587.6968545866041839538.stgit@warthog.procyon.org.uk> <10418.1559084686@warthog.procyon.org.uk> In-Reply-To: To: Jann Horn Cc: dhowells@redhat.com, Al Viro , raven@themaw.net, linux-fsdevel , Linux API , linux-block@vger.kernel.org, keyrings@vger.kernel.org, linux-security-module , kernel list Jann Horn wrote: > I don't really know. I guess it depends on how it's being used? If > someone decides to e.g. make a file browser that installs watches for > a bunch of mountpoints for some fancy sidebar showing the device > mounts on the system, or something like that, that probably shouldn't > inhibit unmounting... I don't know if that's a realistic use case. In such a use case, I would envision the browser putting a watch on "/". A watch sees all events in the subtree rooted at that point and you must apply a filter that filters them out if you're not interested (filter on WATCH_INFO_IN_SUBTREE using info_filter and info_mask). David