lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 29 May 2019 12:16:27 +0100 From: David Howells <dhowells@...hat.com> To: Jann Horn <jannh@...gle.com> Cc: dhowells@...hat.com, Al Viro <viro@...iv.linux.org.uk>, raven@...maw.net, linux-fsdevel <linux-fsdevel@...r.kernel.org>, Linux API <linux-api@...r.kernel.org>, linux-block@...r.kernel.org, keyrings@...r.kernel.org, linux-security-module <linux-security-module@...r.kernel.org>, kernel list <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 3/7] vfs: Add a mount-notification facility Jann Horn <jannh@...gle.com> 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
Powered by blists - more mailing lists