From: Al Viro <viro@zeniv.linux.org.uk>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
James Morris <jmorris@namei.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Matthew Bobrowski <mbobrowski@mbobrowski.org>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
John Johansen <john.johansen@canonical.com>
Subject: Re: fanotify and LSM path hooks
Date: Sun, 14 Apr 2019 20:26:01 +0100 [thread overview]
Message-ID: <20190414192601.GR2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOQ4uxg-NsccKfhzJbZnCnXhKA90VfVdV0_qLRt+8iVa53655g@mail.gmail.com>
On Sun, Apr 14, 2019 at 09:51:38PM +0300, Amir Goldstein wrote:
> But the truth is I would much rather that users have a way to mark
> a subtree root and ask fanotify for events under that subtree.
> As a matter of fact, I have some private POC patches that allow users to
> setup a mark on a "subtree root" dentry, which really marks the super block
> and keep a reference to the dentry. Than every event on that super block
> is filtered with is_subdir() against the marked dentry.
And that is_subdir() is protected by what, exactly? And what happens
if you have many such dentries?
Or, for that matter, what happens if that dentry gets invalidated?
next prev parent reply other threads:[~2019-04-14 19:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 16:04 fanotify and LSM path hooks Amir Goldstein
2019-04-14 16:39 ` Al Viro
2019-04-14 18:51 ` Amir Goldstein
2019-04-14 19:26 ` Al Viro [this message]
2019-04-14 20:28 ` Amir Goldstein
2019-04-16 15:45 ` Jan Kara
2019-04-16 18:24 ` Amir Goldstein
2019-04-17 11:30 ` Jan Kara
2019-04-17 12:14 ` Miklos Szeredi
2019-04-17 14:05 ` Jan Kara
2019-04-17 14:14 ` Miklos Szeredi
2019-04-18 10:53 ` Jan Kara
2020-06-26 11:06 ` fsnotify pre-modify VFS hooks (Was: fanotify and LSM path hooks) Amir Goldstein
2020-06-30 9:20 ` Jan Kara
2020-06-30 14:28 ` Amir Goldstein
2020-07-03 13:38 ` Jan Kara
2020-07-06 10:51 ` Amir Goldstein
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=20190414192601.GR2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
--cc=miklos@szeredi.hu \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=serge@hallyn.com \
--cc=takedakn@nttdata.co.jp \
/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.